about:home's layout-independent initialization tasks should use DOMContentLoaded instead of the load event

RESOLVED FIXED in Firefox 14

Status

()

Firefox
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: dao, Assigned: dao)

Tracking

({perf})

Trunk
Firefox 14
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 606976 [details] [diff] [review]
patch

DOMContentLoaded fires earlier than load.
Attachment #606976 - Flags: review?(mak77)
why do you think we should init earlier? Afaict this has never been reported as a problem, even in the old design that was doing the same.
(Assignee)

Comment 2

5 years ago
I'm not saying I've seen the delay, but that doesn't mean it isn't there. It's probably very short right now, but may get worse soon (bug 697230). Anyway, there's just no reason to wait for the load event with this stuff.
Comment on attachment 606976 [details] [diff] [review]
patch

Review of attachment 606976 [details] [diff] [review]:
-----------------------------------------------------------------

ok, though I'd prefer if this would make its common path to Aurora, to give it some Nightly testing, rather than being backported.  After all we don't evidence we need it urgently.
Attachment #606976 - Flags: review?(mak77) → review+
(Assignee)

Comment 4

5 years ago
http://hg.mozilla.org/integration/mozilla-inbound/rev/c3704b08e87d
Target Milestone: --- → Firefox 14
https://hg.mozilla.org/mozilla-central/rev/c3704b08e87d
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.