Possible to traverse anchors in cached presentations

VERIFIED FIXED

Status

()

VERIFIED FIXED
14 years ago
10 years ago

People

(Reporter: bzbarsky, Unassigned)

Tracking

(Depends on: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
See testcase in URL field.
(Reporter)

Updated

14 years ago
Blocks: 274784
this is wfm (linux)
(Reporter)

Comment 2

14 years ago
Ah, looks like the change to nsGenericElement::ShouldFocus made the exact code
in that testcase not quite work (can't call focus() on the anchor).  I can still
write a testcase that requests expanded privileges and dispatches a trusted
event if desired.  Or we can wait till jst's "make click() work on all HTML
elements" patch lands and then the testcase can just call click().  The key
point is that the anchor knows about the docshell its document used to be in,
but the document isn't in that docshell anymore.
Oh, the |a| variable should go to null when the iframe navigates away? Or should
stay but have no discernible effect?
(and do you have a bug# for that .click() thing?)
(Reporter)

Comment 5

14 years ago
Actually, reading code more carefully I was wrong.  We're now unsetting the link
handler (though not the container?) on the prescontext when we hide in the
SHEntry.  So this actually is fixed.

Ian, the right behavior is that the <a> has no discernible effect.  It should
absolutely not go away.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

14 years ago
Ian, bug 284710.
Not having any effect was what I was hoping you'd say.

Thanks for the link.

VERIFIED fixed.
Status: RESOLVED → VERIFIED
(Reporter)

Updated

14 years ago
Depends on: 293173
(Reporter)

Updated

14 years ago
Depends on: 293175

Updated

10 years ago
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.