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 Score 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 | T272938 Make Score extension compatible with Parsoid |
Event Timeline
Comment Actions
Looking at the Score extension code, it looks like the only markup that is impacted is image linking. But, @Arlolra has been working to have legacy parser generate Parsoid-style output for images. So, we may be have to get away without needing to write a Parsoid-native handler and simply continuing to proxy calls to the legacy parser.
Comment Actions
Just a note that there isn't really a Spec for Score content. Or rather how to distinguish between different types of audio/video (TMH vs Score) content at the spec level.
This should be addressed at some point and leads to problems like T135501: Formalize how TMH provides a player for Score-generated ogg/vorbis files