Page MenuHomePhabricator

[EPIC] Load ResourceLoader startup module from the bottom of the HTML
Closed, DeclinedPublic

Description

Question for Timo...
Is this plausible?
What would be the impact?
Are we crazy?
Why is this currently in the head?

Event Timeline

Jdlrobson raised the priority of this task from to Needs Triage.
Jdlrobson updated the task description. (Show Details)
Jdlrobson added subscribers: Mholloway, Ricordisamoa, He7d3r and 8 others.

It's in the head because of these modules being loaded in the head:

view-source:https://en.m.wikipedia.org/wiki/Main_Page

mw.loader.load([
 "mediawiki.page.startup",
 "mobile.head",
 "mobile.site",
 "ext.centralNotice.bannerController.mobiledevice",
 "ext.centralNotice.bannerController.mobile",
 "ext.centralNotice.bannerController.lib",
 "ext.centralNotice.bannerChoiceData",
 "ext.centralauth.centralautologin.clearcookie",
 "ext.imageMetrics.head"
]);
phuedx renamed this task from Can we move ResourceLoader startup module on mobile to the bottom of the page. to [EPIC] Can we move ResourceLoader startup module on mobile to the bottom of the page..Jun 1 2015, 10:13 AM
phuedx set Security to None.
phuedx moved this task from Incoming to 2015-16 Q2 on the Readers-Web-Backlog board.
Krinkle renamed this task from [EPIC] Can we move ResourceLoader startup module on mobile to the bottom of the page. to [EPIC] Load ResourceLoader startup module from the bottom of the HTML.Jun 1 2015, 12:53 PM

@Jdlrobson Is this feasible?

I've added the blocking tasks. Couldn't find anything for "mediawiki.page.startup" and "mobile.head".

Probably not at current time given we have no control over ext.centralNotice and mediawiki.page.startup
We could however explore moving all mobile code to bottom.

Jhernandez added a comment.EditedAug 17 2015, 9:26 AM

If it is worth it would you mind putting your thoughts into a task/spike as a blocker of this one @Jdlrobson?

Jhernandez triaged this task as Medium priority.Aug 17 2015, 11:39 AM
Jhernandez edited projects, added MobileFrontend; removed Readers-Web-Backlog.

Unfortunately mediawiki.page.startup is not within our control, and I'd suggest the performance team evaluate if it makes sense.

The central notice resources should be addressed in a CentralNotice refactor.

Mobile.site and mobile.head are in our control and we should think about what we gain and lose with these (the former is happening this sprint but mobile.head will have some consequences on reducing interactive time).

Jdlrobson closed this task as Declined.Oct 9 2017, 5:04 PM