Closed
Bug 966573
Opened 10 years ago
Closed 9 years ago
Use speculative connections for URLs coming into BrowserCLH.js
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 30
People
(Reporter: mfinkle, Assigned: mfinkle)
References
Details
Attachments
(1 file)
1.05 KB,
patch
|
wesj
:
review+
|
Details | Diff | Splinter Review |
If we get an external URL in BrowserCLH.js, we will probably end up loading it in a <browser>. Let's use nsISpeculativeConnect to remove some of the networking startup. Let's be sure that using nsISpeculativeConnect doesn't cause a startup regression.
Assignee | ||
Comment 1•10 years ago
|
||
Simple patch.
Assignee: nobody → mark.finkle
Attachment #8369747 -
Flags: review?(wjohnston)
Updated•10 years ago
|
Attachment #8369747 -
Flags: review?(wjohnston) → review+
Assignee | ||
Comment 2•9 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/c95d496bb270
https://hg.mozilla.org/mozilla-central/rev/c95d496bb270
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•