Go to http://fr.m.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil%20principal?title=Wikip%C3%A9dia:Accueil_principal&mobileaction=toggle_view_mobile in beta mode
Open console
I get the error ""Uncaught ReferenceError: wgPageContentLanguage is not defined"
Version: unspecified
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44070
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T76456 Language Engineering tracker of trackers (tracking) | |||
| Resolved | Nikerabbit | T55015 Font support in Universal Language Selector (tracking) | |||
| Declined | None | T30515 Dynamic fonts support in mobile frontend extension | |||
| Resolved | Jdlrobson | T46017 Leverage browser cache for JS and CSS (separate requests for common and page-specific things) | |||
| Resolved | None | T31713 Extensions that need resource loader-ifying (tracking) | |||
| Resolved | Jdlrobson | T46070 Dynamically loading SpecialPage ResourceLoader modules causes unnecessary processing on ALL requests | |||
| Resolved | None | T46072 RL modules specifying 'position' => 'bottom' aren't loading | |||
| Resolved | None | T43340 MobileFrontend: Implement ResourceLoader (tracking) |
That doesn't look like a ResourceLoader environment.
Where is the startup module, its mw.config and the page-specific and user-specific mw.config and mw.user output from OutputPage?
(In reply to comment #1)
That doesn't look like a ResourceLoader environment.
Where is the startup module, its mw.config and the page-specific and
user-specific mw.config and mw.user output from OutputPage?
Ah, I didn't enter "beta" mode (via search menu, Configurations, toggle "Beta", save, reload).
Okay, so it does output the startup module, but does so incorrectly and the rest of the environment does indeed not look like how ResourceLoader presents it self usually (appears re-invented/hardcoded for mf).
OutputPage does / ResourceLoader expects:
Right now MF does:
Tracking down the error in particular it looks like "Uncaught ReferenceError: wgPageContentLanguage is not defined" is just the first in a long sequence of errors caused by the invalid environment.
OutputPage does / ResourceLoader expects:
- startup module in the <head> before any load.php script
- <head> needs to contain mw.user and mw.config
- <head> will output top queue (if any)
- <body> will output bottom queue
Also: oldschool raw styles/scripts added by extensions in head/body respectively, such as geoiplookup in CentralNotice which provides the "Geo" global variable.
Right now MF does:
- startup module at bottom of <body>
- <body> will output bottom queue
Tracking down the error in particular it looks like "Uncaught ReferenceError:
wgPageContentLanguage is not defined" is just the first in a long sequence of
errors caused by the invalid environment.
ResourceLoader is now implemented in mobile. There are a few bugs to perfect it's implementation. I don't think the existence of this tracking bug is useful anymore. Feel free to disagree.
jgonera wrote:
I'm afraid there is still something we're missing. JavaScript tests page loads JS at the bottom instead of top (as it does in desktop) for some reason which breaks PhantomJS runner after applying this changeset: https://gerrit.wikimedia.org/r/#/c/50442/