https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
Gilles Dubuc gdu...@wikimedia.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
Gilles Dubuc gdu...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
--- Comment #7 from Gilles Dubuc gdu...@wikimedia.org ---
And by replay I mean that it would of course swallow the original click that
happens before the DOM is ready and replay it on DOM readiness. I didn't mean
having the event twice for a
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
--- Comment #5 from Mark Holmquist mtrac...@member.fsf.org ---
Actually, I may have been thinking about this wrong - we *do* change visual
things above the fold when a hash fragment is detected, so maybe we should
actually be top-loading.
We
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
--- Comment #1 from Mark Holmquist mtrac...@member.fsf.org ---
I don't think we can do anything currently to make the loading any faster, but
Gilles may beg to differ.
FWIW I asked Krinkle about loading MMV top-side and he said it wasn't
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
Dan Garry dga...@wikimedia.org changed:
What|Removed |Added
Priority|Unprioritized |Low
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
--- Comment #3 from Tisza Gergő gti...@wikimedia.org ---
MMV is just a 16K bootstrap file now, so top-loading it does not sound that bad
to me. I don't see other options apart from wontfixing this - until it is not
loaded, we cannot interfere
https://bugzilla.wikimedia.org/show_bug.cgi?id=62540
Dan Garry dga...@wikimedia.org changed:
What|Removed |Added
CC||krinklem...@gmail.com
