Parsoid has a different extension "hooks" mechanism and a different parser API for extensions. This is being implemented in code, prototyped via Parsoid's implementation of extensions (currently in Parsoid's repository) and being documented at https://www.mediawiki.org/wiki/Parsoid/Extension_API
This will have to go through a period of feedback and refinement but given the scope and magnitude of changes for extensions, this has to go through the TechCom RFC process.
| 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 | |||
| Resolved | • ssastry | T253769 File an RFC about Parsoid Extension API |
https://etherpad.wikimedia.org/p/wikimania2017_hackathon_parser_hooks from T172817 is worth taking a look as well here.