Closed
Bug 736848
Opened 13 years ago
Closed 13 years ago
about:home's layout-independent initialization tasks should use DOMContentLoaded instead of the load event
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
FIXED
Firefox 14
People
(Reporter: dao, Assigned: dao)
Details
(Keywords: perf)
Attachments
(1 file)
|
2.07 KB,
patch
|
mak
:
review+
|
Details | Diff | Splinter Review |
DOMContentLoaded fires earlier than load.
Attachment #606976 -
Flags: review?(mak77)
|
||
Comment 1•13 years ago
|
||
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•13 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 3•13 years ago
|
||
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•13 years ago
|
||
Target Milestone: --- → Firefox 14
|
||
Comment 5•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•