Background
I assume it will be easier for all parties involved if all editor related code is in a single repository (perhaps VisualEditor?). This means very clear code boundaries and clearer contracts between teams.
Doing this will also allow us to evolve the editor code away from MobileFrontend's libraries towards OOUI and/or Codex.
User story
As a developer I want all editing code in one place.
Requirements
- Move all editing code into mobile.init/editor.js (which in future will be the packageFile index file) https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MobileFrontend/+/1196766
- We reduce MobileFrontend dependencies for editing code in mobile.init with non-MobileFrontend
- util
- IconButton, Icon
- OverlayManager
- (optional) we remove use of MobileFrontend Overlay for an OO.ui.Dialog
- We pull out editing code from mobile.init module into mobile.editor.init
- We add a new module to VisualEditor to replace mobile.editor.init and copy the new module across verbatim
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