Rather than load a JavaScript message parsing library, the mobile site pre-parses certain messages before passing them via ResourceLoader to the client:
We should add support to ResourceLoaderFileModule for this.
Implementor: Please be sure to talk to someone in editing and agree on the approach before pushing a patch.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T158181 Aim for workflow equivalence for MediaWiki on desktop and mobile web | |||
| Resolved | Jdlrobson | T71366 [EPIC] Extract Minerva skin from MobileFrontend to its own repository | |||
| Duplicate | None | T104474 Add support for parsed messages in ResourceLoader (push to core) |
VisualEditor also does something like this, for messages which can't be parsed client-side (e.g. likely to contain wikitext templates).
CONTENTLANG, SITENAME and int:mobile-frontend-search-content are the only things we parse right now. So we don't pre-parse anything which requires parameters (but the client wouldn't be able to translate these effectively)
I am not a fan of MF's current syntax of 'foo' => array( 'parse' ). I think having a separate 'parsedmessages' key might be better.
How does the MF implementation deal with cache invalidation of links/templates in the parsed message?
Hmm, losing support for message parameters looks like a pretty big caveat worth mentioning.