Background
As we've moved towards Parsoid the PageHTMLParser has become more complex. In current form it caters for:
- $wgParserEnableLegacyHeadingDOM = true (WMF production with legacy parser)
- $wgParserEnableLegacyHeadingDOM = true; (third party support)
- $wgParserEnableLegacyHeadingDOM = false and Parsoid (WMF production with Parsoid enabled)
- Desktop HTML (used by <1% of logged in users who have switched to Minerva desktop as their preferred skin)
it's proposed to simplify this code so it only caters for 1 and 3.
This should also address the issues in page issues described in T388696.
User story
As a developer I want easier to maintain code
Requirements
- PageHTMLParser code has been updated to reflect modern HTML (it is currently written for $wgParserEnableLegacyHeadingDOM = false)
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous