Background
This is follow up work to T366419 and T362332. The current state of code does not clearly separate the reference preview code from page previews, meaning changes in page preview can impact the issue. These should be decoupled.
User story
As a member of the web team I want to feel safe making changes to my codebase without impacting another team's feature.
Requirements
- Reference previews preferences live in Cite: The Popups extension defines 2 preferences: popups-reference-previews and popupsreferencepreviews. We were about to remove these, but realized the Cite extension has not defined those itself. https://github.com/wikimedia/mediawiki-extensions-Popups/blob/aa514c485d74932f596dae71ae55fb5c1cd7b5de/extension.json#L216
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.0.0 of the Web team task template using phabulous