Parsoid/Parser Unification/Known Issues
This page lists known issues and missing functionality that a typical reader or editor will notice when using the ParserMigration extension to use the Parsoid wikitext parser when viewing articles and talk pages. For a more technical overview of the differences between Parsoid-generated HTML and HTML generated by the legacy parser, see Known differences with Core Parser output.
How to verify and report an issue not listed below
[edit]Before reporting an issue,
- Click the "Use legacy parser" link in the user tools sidebar and verify that your issue is indeed Parsoid-related.
- Purge the cache to regenerate Parsoid HTML that may have been from an older version and check if the issue persists.
If you do not see your issue in the list below, please report it on Phabricator (see Phabricator/Help) or on this discussion page.
Known issues
[edit]The following issues are known and expected to be fixed in the weekly version of MediaWiki; check the release schedule and the current version running on your wiki for timing:
- ...
The following additional issues are known:
- T278481 - Various issues with Proofread Page on wikisource wikis
- T348722 - Phab page indicator template broken on some wikis
- T356718 - Special page transclusions nested in templates
- The ListingEditor2023 gadget used on English Wikivoyage is not yet compatible with Parsoid. Use the
ListingEditor2023-Beta
gadget, available from your user preferences. - T373400 - some section links are skipped in mapbanner
- T372608 - Not all GeoData errors are displayed
- T374868 - Non-existing media links are not redlinks in Parsoid
- T374532 - After switch from parsoid to legacy mode, and edit, page not reloaded in legacy mode
- Duplicate IDs on a page may cause issues
- T374724 - issue with leading colon in LST
<section>
- T368724 - broken template transclusion rendering differs from legacy
- T370751 - Parsoid breaks next-sibling TemplateStyles hack
- T375981 - Parsoid doesn't respect user media size preferences
In addition, the following issues are known differences between Parsoid and the legacy parser and are not expected to be fixed: