Background
When Parsoid is the default for mobile (T422543: Deploy Parsoid Read Views to MobileFrontEnd readers on enwiki) the Readers Growth team will need to determine what support level they want to give the legacy parser in MobileFrontend and for how long.
Removing support for the legacy parser, will remove section collapsing and lazy loaded images but will remove many thousand lines of code.
User story
- Add user story in the format: “As a [persona], I want to [X], so that [Y]”
Requirements
- Decide level of support for legacy parser
- delete or deprecate unnecessary code.
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
- Add 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