Impacted extensions will lose message box styling without taking any action so it is important that teams prioritize this ticket.
== Background
Historically code has used mw-message-box for styling message boxes.
As part of standardization to Codex, this markup must now be transitioned to CdxMessage markup:
https://doc.wikimedia.org/codex/latest/components/demos/message.html#markup-structure
If extensions are using Html::messageBox there is nothing to do here.
Extensions using JavaScript to create message box should either switch to Codex or alter their markup:
Currently to mitigate impact Vector 2022 skin loads the old styles via JavaScript but we would like to remove this in future.
== TODO
Impacted code https://codesearch.wmcloud.org/deployed/?q=mw-message-box and https://global-search.toolforge.org/?q=mw-message-box®ex=1&namespaces=&title=
Phase 1: updates to extensions
[x] MobileFrontend
[x] CentralNotice
[x] Gadgets (user notice)
[x] FlaggedRevisions
[x] GrowthExperiments
[] MassMessage
[] TwoColConflict
[x] Minerva will drop support for the legacy message styles.
## Deprecated extensions
The following extensions are being sunset so will not be migrated and will lose styling:
[] Flow
[] Graph
# When this task is resolved
Create new tickets for:
[x] Remove loading of message box styles via JavaScript in Vector and Minerva.
[] Make sure callers of Html::messageBox are also adding appropriate Codex styles to the page (https://phabricator.wikimedia.org/T375246)
[] Update markup in core to remove references to old non-Codex classes.