Closed
Bug 312117
Opened 19 years ago
Closed 19 years ago
target="_top" links in an iframe are invalidated with bfcache on (or off)
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
VERIFIED
FIXED
mozilla1.9alpha1
People
(Reporter: ispiked, Assigned: bryner)
References
Details
(Keywords: regression, Whiteboard: [Regression/Bug 292962 checkin happened on 2005-10-07 afternoon])
Attachments
(3 files)
235 bytes,
text/html
|
Details | |
255 bytes,
text/html
|
Details | |
3.84 KB,
patch
|
sicking
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
If a link within an <iframe> has target="_top" and one views that link, then
goes back to the page with the iframe, links with target="_top" in that iframe
will not open in the current, full window, but rather within the iframe.
Steps to reproduce:
1. Open up the testcase and click the link to Slashdot.
2. Go back to the testcase without clicking any other links.
3. Click the Slashdot link again.
The Slashdot homepage is loaded within the iframe when it should be loaded into
the current window/tab as it did to begin with. This is not an issue with
max_viewers set to 0.
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Comment 3•19 years ago
|
||
Why am I your default fall man? bfcache is all bryner.
bryner, it sounds like we're not setting the right tree owner or parent on those
docshells or something?
Component: General → History: Session
Product: Firefox → Core
QA Contact: general → history.session
Comment 4•19 years ago
|
||
Yeah.
(gdb) frame
#0 nsDocShell::FindItemWithName (this=0x88efa28, aName=0xbfffe968, aRequestor=0x0,
aOriginalRequestor=0x88efac4, _retval=0xbfffe7d0)
at ../../../mozilla/docshell/base/nsDocShell.cpp:2074
2074 GetSameTypeRootTreeItem(getter_AddRefs(foundItem));
(gdb) p mParent
$2 = (nsDocLoader *) 0x0
That's not good at all -- some of our security checks use the docshell
hierarchy, and you can do things to parentless docshells that you can't do to
ones with parents.
Assignee: nobody → bryner
Flags: blocking1.8rc1?
Updated•19 years ago
|
Flags: blocking1.8rc1? → blocking1.8rc1+
Assignee | ||
Comment 5•19 years ago
|
||
This is a recent regression from sicking's checkin for bug 292962. The child
shells list in the SHEntry is getting cleared out by SetContentViewer(null) in
RestoreFromHistory, but we want to use the list of child shells after that.
However, this problem should not happen on the branch, because the lower-risk
patch we landed there does not call DropPresentationState from SetContentViewer.
Re-setting the blocking1.8rc1 flag since I don't think this impacts the branch.
Assignee | ||
Comment 6•19 years ago
|
||
I just verified on a branch build that the problem doesn't happen.
Removing nomination since this doesn't happen on branch.
Flags: blocking1.8rc1?
Comment 8•19 years ago
|
||
Er... didn't we just back out bug 292962 from the branch altogether? And aren't
we planning to reland it there now that we have bug 311269 fixed? Certainly bug
292962 is still blocking1.8rc1+.
Depends on: 292962
Updated•19 years ago
|
Yes, 292962 was backed out alltogether. And I don't think that the part that did
land there would have caused this bug (can't tell for sure until I have looked
into this)
Comment 10•19 years ago
|
||
*** Bug 313166 has been marked as a duplicate of this bug. ***
Comment 11•19 years ago
|
||
I'm upping this to critical severity given the role that parent chains play in
security checks.
Severity: normal → critical
Flags: blocking1.9a1?
Comment 12•19 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051013 SeaMonkey/1.1a]
(nightly) (W98SE)
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051021 SeaMonkey/1.1a]
(nightly) (W98SE)
(I see this bug/testcase, and)
I believe I'm seeing this/same bug with regular frameset/frames on ("private")
<www.battle-arenas.net>.
Whiteboard: [Regression/Bug 292962 checkin happened on 2005-10-07 afternoon]
Comment 13•19 years ago
|
||
(In reply to comment #12)
> (I see this bug/testcase, and)
> I believe I'm seeing this/same bug with regular frameset/frames on ("private")
> <www.battle-arenas.net>.
Bug started with
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051008 SeaMonkey/1.1a] (nightly) (W98SE)
(testcase and wBAn site) Occurs with
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051022 SeaMonkey/1.1a] (nightly) (W98SE)
even with |user_pref("browser.sessionhistory.max_viewers", 0);|
Comment 14•19 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051030 SeaMonkey/1.1a] (nightly) (W98SE)
Help, this is still preventing me from using SMv1.1a Trunk builds :-(
(upping Severity to Blocker)
Severity: critical → blocker
Summary: target="_top" links in an iframe are invalidated with bfcache on → target="_top" links in an iframe are invalidated with bfcache on (or off)
Comment 15•19 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051104 SeaMonkey/1.1a] (nightly) (W98SE)
Blocker weekly report: still there.
Assignee | ||
Updated•19 years ago
|
Assignee: bugmail → bryner
Assignee | ||
Comment 16•19 years ago
|
||
Get all of the state off the SHEntry before we clear its content viewer.
Attachment #202049 -
Flags: superreview?(bzbarsky)
Attachment #202049 -
Flags: review?(bugmail)
Comment 17•19 years ago
|
||
Comment on attachment 202049 [details] [diff] [review]
fix
>Index: nsDocShell.cpp
> // Reattach to the window object.
> rv = mContentViewer->Open(windowState, mLSHE);
Please add asserts after this line that:
1) mLSHE's refresh URI list is null.
2) mLSHE->ChildShellAt(0) returns null.
With those, sr=bzbarsky
Attachment #202049 -
Flags: superreview?(bzbarsky) → superreview+
Comment on attachment 202049 [details] [diff] [review]
fix
Thanks for taking care of this!
Attachment #202049 -
Flags: review?(bugmail) → review+
Has somebody double-checked that this doesn't happen on the 1.8 branch with what's now landed there?
Comment 20•19 years ago
|
||
(In reply to comment #19)
> Has somebody double-checked that this doesn't happen on the 1.8 branch with
> what's now landed there?
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051107 SeaMonkey/1.0b] (release) (W98SE)
Never (since comment 12) had this bug, per testcase or wBAn site.
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051108 SeaMonkey/1.5a] (nightly) (W98SE)
(still buggy, per testcase)
Assignee | ||
Comment 21•19 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Target Milestone: --- → mozilla1.9alpha
Comment 22•19 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051109 SeaMonkey/1.5a] (nightly) (W98SE)
V.Fixed, per testcase.
Status: RESOLVED → VERIFIED
Flags: blocking1.9a1?
Comment 23•19 years ago
|
||
*** Bug 314252 has been marked as a duplicate of this bug. ***
No longer blocks: 314252
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•