Currently, some code uses ParserOptions::getUserLang, while most code relies on Context::getLanguage; even ParserOptions::getTargetLanguage was used at some point.
We need to consistently use ParserOptions::getUserLang when generating page content, as to not poison the parser cache.
Version: unspecified
Severity: major
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T59765 Provide JavaScript hook | |||
| Resolved | Lydia_Pintscher | T63131 Eliminate or reduce delay between selection of property and displaying of input fields when adding statements | |||
| Resolved | None | T58090 Do not change targets to javascript:void(0); on JavaScript load for various "edit" links | |||
| Invalid | None | T56098 [Epic][UI] Front-end performance: Improve loading time of items | |||
| Resolved | None | T59746 Allow Entity pages to be stored in the ParserCache | |||
| Resolved | None | T60344 Consistently use ParserOptions::getUserLang for generating entity pages |
Change 100829 had a related patch set uploaded by Daniel Kinzler:
(bug 58344) use getUserLang for EntityView