The ParserMigration extension was deployed during 2017 (T141586) to compare legacy Tidy-based output with the Remex-based replacement, to aid in migration to the new tidy algorithm. It was undeployed in Dec 2018 after that migration was complete.
It was overhauled in 2023 to compare Parsoid output with the legacy wikitext parser output (T333177), as part of the Parsoid-Read-Views project, and the Content-Transform-Team would like to redeploy it to production.
The README and on-wiki Help:Extension:ParserMigration provide more information on the operation and purpose of this extension.
Testing ParserMigration
You can follow the instructions at Help:Extension:ParserMigration to enable the user preference and then view the side-by-side comparison output of (for example) the Main Page.
Special:ApiSandbox can also be used to verify that the action API component is working: action=parser-migration.
Needed for deployment of the ParserMigration extension
- Security Review (T334962): this was done for the 2017 deployment (T141591#2609752) but requires an update; note that part of the previous review was Html5Depurate which became Remex and remained in production as part of core even after ParserMigration was undeployed; the new extension is lighter-weight than the original since the basic functionalities it is using are already part of core.
- (Re)start branching ParserMigration (blocked on security review): https://gitlab.wikimedia.org/repos/releng/release/-/merge_requests/30
-
Design Review: this is intended primarily for internal use -
Performance Review: part of the purpose of deploying this extension is to allow Content-Transform-Team to benchmark Parsoid rendering under realistic conditions for production read views - Deploy on beta sites
- Deploy on test wikis
- Deploy on all wikis