- Emit NewPP report data as "configuration" variables
- Use the configuration variable and output the result in the Performance inspector.
This change should go out the same time as we push the inspector so it's easy to use the new format.
This change should go out the same time as we push the inspector so it's easy to use the new format.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | • aripstra | T138621 Evaluate UX/Design for Performance Inspector | |||
Declined | None | T130581 Performance inspector on mobile | |||
Resolved | Peter | T117411 Launch on-wiki page performance inspector | |||
Resolved | aaron | T110763 Include NewPP report as a JSON configuration object |
Change 294292 had a related patch set uploaded (by Phedenskog):
Include the NewPP report in Performance inspector
This is trickier than I initially thought. The parser currently adds the report to the page HTML. Adding the report as a JavaScript config script is not a simple change, because JavaScript config scripts are not part of the parser output; they're part of the interface.
So, I think the right way to do this is to leave performance data in the parser output as data, and leave it up to the interface code to extract this data and expose it to users. This should be done in OutputPage.php, most likely.
Change 299693 had a related patch set uploaded (by Aaron Schulz):
Move NewPP limit report HTML comments to JS variables
Change 299693 merged by jenkins-bot:
Move NewPP limit report HTML comments to JS variables
Change 294292 merged by jenkins-bot:
Include the NewPP report in Performance inspector
Change 320461 had a related patch set uploaded (by Bartosz Dziewoński):
Revert "Move NewPP limit report HTML comments to JS variables" and followups
I am reverting this due to numerous regressions – see T142210 and the patches linked there for details. I think a machine-readable limit report would be a very useful feature, but not at the cost of losing the human-readable limit report, as it was implemented here.
(PerformanceInspector is not yet deployed to WMF production, as far as I know, so this shouldn't be problematic for day-to-day operations of the sites. But I'm doing this after a branch cut just in case.)
Change 320461 merged by Bartosz Dziewoński:
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320522 had a related patch set uploaded (by Bartosz Dziewoński):
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320522 merged by Bartosz Dziewoński:
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320861 had a related patch set uploaded (by Aaron Schulz):
Include JS variable for NewPP report