Parsoid has its own extension API - see https://www.mediawiki.org/wiki/Parsoid/Extension_API.
In this first phase, we are targeting tag-hook extensions for migration.
The Listings extension needs an update to work directly with Parsoid.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Release | None | T84936 Release VisualEditor-MediaWiki as "1.0" | ||
| Open | None | T50429 [Epic] Support editing parts of a page in VisualEditor-MediaWiki | |||
| Open | None | T54365 Explore performance gains from progressive (JIT?) de-alienation in VisualEditor | |||
| Open | None | T174303 Copy-pasting linked ISBN numbers from view mode HTML into VisualEditor inserts wikitext links to Special:BookSources (it should turn them into magic links?) | |||
| Open | Feature | None | T54091 The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces | ||
| Open | None | T55784 [EPIC] Use Parsoid HTML for all page views | |||
| Open | None | T258838 [EPIC] Ensure all extensions on the Wikimedia cluster that use Parser hooks or implement tag hooks are retargeted for Parsoid | |||
| Open | None | T272937 Make Listings extension compatible with Parsoid |
Event Timeline
Comment Actions
Looks likes this builds up a bunch of wikitext and then parses it to HTML. This is only enabled on wikivoyages except (en, de, it). This looks like a fairly straightforward (if a bit cumbersome) port to Parsoid.
Comment Actions
Considering that we plan to only have enwikivoyage for phase 1, should we move this to a different phase?