Closed
Bug 297202
Opened 20 years ago
Closed 19 years ago
Unreliable DOM access with back-forward cache and frames
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dpoon, Unassigned)
Details
(Keywords: testcase)
Attachments
(4 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+
With the blazingly fast back-forward feature, under certain conditions,
attempted cross-frame DOM access fails. See the attached test case.
Reproducible: Always
Steps to Reproduce:
0. Put the three files of the attached test case in the same directory, either
on the local disk or on a webserver. (With a webserver, it doesn't matter
whether the Content-Type is text/html or application/xhtml+xml -- they both
fail.) Bring up frameset.html.
1. In about:config, set browser.sessionhistory.max_viewers to 5 as suggested,
restart Deer Park, then load this test case again.
2. Click on button 1, and get JavaScript alert as expected.
3. Go elsewhere, then hit the Back button.
4. Click on button 1 again, and notice that it does nothing. However, button 2
(which is identical) still works.
5. Start from a clean slate by Shift-Reloading the frameset.
6. Click on button 1 again, and get JavaScript alert as expected. Also click on
button A.
7. Go elsewhere, then hit the Back button.
8. Try clicking on all four buttons. This time, they all work!
9. Unset browser.sessionhistory.max_viewers, restart Deer Park.
10. Repeat steps 2-4. This time, all of the buttons work as well.
Actual Results:
Failure in step 4, as noted.
Expected Results:
All buttons should show a JavaScript alert when clicked.
100% reproducible on my Deer Park RC1 (2005-05-31, precompiled package from
mozilla.org) on Mac OS 10.4.1. I haven't tried on any other setup. The bug
sometimes disappears when the test case becomes more complex.| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
| Reporter | ||
Comment 3•20 years ago
|
||
| Reporter | ||
Comment 4•20 years ago
|
||
| Reporter | ||
Comment 5•20 years ago
|
||
I forgot to mention, I have no extensions installed.
Updated•20 years ago
|
Component: History → History: Session
Keywords: testcase
Product: Firefox → Core
QA Contact: history → history.session
Version: unspecified → 1.0 Branch
Updated•20 years ago
|
Version: 1.0 Branch → Trunk
| Reporter | ||
Comment 6•19 years ago
|
||
I just tried the test case with Firefox 1.5 beta 1 on Mac OS, and couldn't reproduce the bug. I assume it has been fixed somehow.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 7•19 years ago
|
||
No specific bug / patch referenced as the fix. -> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
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
•