Closed Bug 764931 Opened 13 years ago Closed 13 years ago

Don't use about:newtab for nsBrowserAccess

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 16

People

(Reporter: ttaubert, Assigned: ttaubert)

References

Details

(Whiteboard: [fixed-in-fx-team])

Attachments

(1 file)

Attached patch patch v1Splinter Review
nsBrowserAccess is (if I understood the code correctly) only used to open links with custom target attributes in a new window or new tab. We should continue to use about:blank as default here instead of about:newtab because that new docShell/window will be used to load a new link in it and there's no need to load about:newtab in there. While working on bug 753448 I noticed the following assertion: http://mxr.mozilla.org/mozilla-central/source/dom/base/nsGlobalWindow.cpp#1471 This happens because we're opening a new tab and will be loading about:newtab and thus swapping a preloaded page. So it's actually more a timing issue that we didn't hit this assertion so far, I think.
Attachment #633199 - Flags: review?(gavin.sharp)
Assignee: nobody → ttaubert
Status: NEW → ASSIGNED
Comment on attachment 633199 [details] [diff] [review] patch v1 Good catch; the only caller that passes null that I could find was nsContentTreeOwner::ProvideWindow, which indeed really specifically wants about:blank.
Attachment #633199 - Flags: review?(gavin.sharp) → review+
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 16
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.

Attachment

General

Created:
Updated:
Size: