This task is for design review and potential UX updates to the ParserMigration notice, which was added in T355567 and made Codex-compliant in T358296, T359000. Some slack discussion is at https://wikimedia.slack.com/archives/C024QCFAJ/p1706624320880659, https://wikimedia.slack.com/archives/C024Z8K9CAU/p1708637580424359, and https://wikimedia.slack.com/archives/C05D7UDJZ5E/p1713985199324989, summarized below.
The goal of the UX feature is to ensure that readers are aware that the Parsoid migration may cause issues with the display of certain articles on-wiki, and to ensure that they have access to links to provide more information or to report bugs if they find them. Since on some wikis parsoid is not used on every page (for example, it is being deployed only on talk pages which use discussion tools on some wikis), there should be some subtle indication on the page when parsoid is being used.
Our current design:
- Puts a "Rendered with Parsoid" page indicator at the top of a page rendered with Parsoid, using the Codex InfoChip CSS (this is a slight violation of design guidance for the use of this component)
- Add a notification popup the first time a user visits a page rendered with Parsoid, containing links to more information about the feature and a place to report bugs.
- When the notification is dismissed, it stays dismissed for "some time" (currently 7 days, soon 30 days) but the idea was that it would periodically reappear in case the original notice was dismissed accidentally (aka "oops, now i'll never see that again").
Initial feedback was that the mechanism to dismiss the dialog wasn't very discoverable (T358296) which I think has now been addressed, although not in a generic way that benefits other users of mw.notification (T42307). More recent feedback has been that the notification "keeps reappearing", which might be because the cookie is site-specific, and so when you log in to a different domain (mobile vs desktop, en versus wikitech versus officewiki) you get the notice again. It might also be that the 7 day timeout is too short, or that there is some other bug in the cookie mechanism.
Some questions:
- Could the wording be improved? Does an ordinary user know what the "Rendered With Parsoid" infochip means? Does the wording in the popup notification communicate what we are trying to convey?
- Perhaps the "link for more information" could be folded into the page indicator infochip somehow; I don't think there's existing Codex guidance for this though.
- Perhaps a site notice or other static message is more appropriate that a pop up notification?
- Perhaps the popup notification itself could be less obtrusive?
- Perhaps this should look different on mobile than desktop -- the popup takes up a much larger fraction of screen real estate on mobile.
To reproduce: follow the instructions at https://www.mediawiki.org/wiki/Help:Extension:ParserMigration to enable parsoid read views for a wiki (or globally).
