Last modified: 2014-05-30 17:42:11 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57524, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55524 - Enforce proper nesting of most templates, and encapsulate compound content blocks
Enforce proper nesting of most templates, and encapsulate compound content bl...
Status: NEW
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Gabriel Wicke
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-09 19:00 UTC by Gabriel Wicke
Modified: 2014-05-30 17:42 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Gabriel Wicke 2013-10-09 19:00:28 UTC
Transclusions can currently affect arbitrary parts of the page by producing unbalanced HTML. This makes both WYSIWYG editing and efficient updates difficult. We would thus like to move towards properly nested templates as much as possible. For existing multi-transclusion content we would like to enforce nesting as a unit, possibly using a <domparse> extension-like tag wrapping such a content block. This would still let us reuse expansions for multi-template content, which is important for large list pages like http://fr.wikipedia.org/wiki/Liste_des_premiers_pr%C3%A9fets_fran%C3%A7ais_(1800-1815).

The solution should:
* work with old and new revisions, with predictable HTML diff behavior
* support multi-transclusion/extension content reuse
* support a mix of transclusions, extension tags and page content
* work well with the VisualEditor preview
Comment 2 Gabriel Wicke 2013-12-03 22:22:55 UTC
Lowering the priority a bit, as other issues are more pressing currently.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links