This is needed to allow VisualEditor to support such lovely wikitext as {{echo|{{echo|Foo!}}}} and more complex variations.
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz69870
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Release | None | T84936 Release VisualEditor-MediaWiki as "1.0" | ||
| Open | None | T85477 Allow to add special characters to infoboxes, citation templates, and other templates | |||
| Open | None | T55613 Create dedicated input methods for transclusion parameters (using "Param#type" from TemplateData) | |||
| Open | Feature | None | T52182 VisualEditor: Add support for making some templates directly "visually editable" in the DOM, as if they were tables (e.g. infoboxes) | ||
| Open | None | T52355 VisualEditor: Add support for editing templates' parameters as DOM elements ("visually"), including supporting nested templates | |||
| Open | Feature | None | T71870 Enable DOM editing of transclusion parameters | ||
| Declined | None | T85937 Parallelize template or template parameter expansion |
Event Timeline
Comment Actions
The current status for DOM transclusion parameters is: The code is there, but it is disabled by default as it affects performance. For example, it increases the rendering of [[Barack_Obama]] by more than 3s.
To enable it (in case someone wants to try it out), add
parsoidConfig.addHTMLTemplateParameters = true;
to localsettings.js.
With this enabled, it's possible to make Parsoid accept new transclusion parameters from HTML by removing the wt ones. We are also planning on adding support for detecting changes in parameters (so that the wikitext ones don't have to be removed) in the future.
I'll be working on improving performance shortly.
Comment Actions
(In reply to Marc Ordinas i Llopis from comment #1)
With this enabled, it's possible to make Parsoid accept new transclusion
parameters from HTML by removing the wt ones. We are also planning on adding
support for detecting changes in parameters (so that the wikitext ones don't
have to be removed) in the future.
That sounds great.
I'll be working on improving performance shortly.
Excellent. :-)
Comment Actions
A different approach that we have considered over the last few months is to generate these HTML representation of tpl params on demand rather than for Parsoid to generate this all the time and then store it.
So, whenever a template is opened up for editing in VE, VE would request Parsoid for HTML representation of these parameters, and then use that to enabled HTML editing of these params. If this is considered a workable approach, we can work out the details and this can see the light of day much faster.