Closed Bug 387979 Opened 17 years ago Closed 17 years ago

Can't access about:blank iframe after reload

Categories

(Core :: DOM: Core & HTML, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: moz_bug_r_a4, Assigned: bzbarsky)

References

Details

(Keywords: fixed1.8.0.13, regression, verified1.8.1.5)

Attachments

(2 files, 1 obsolete file)

Attached file testcase
This seems to be a regression from bug 381300. http://bonsai.mozilla.org/cvsquery.cgi?module=AviarySuiteBranchTinderbox&branch=MOZILLA_1_8_BRANCH&date=explicit&mindate=2007-07-11+03&maxdate=2007-07-12+03 fx2.0.0.5pre 2007-07-11-03 Before reload: [object HTMLBodyElement] After reload: [object HTMLBodyElement] fx2.0.0.5pre 2007-07-12-03 Before reload: [object HTMLBodyElement] After reload: Permission denied to get property HTMLDocument.body
Looking into this...
Assignee: nobody → bzbarsky
Blocks: 81300
Flags: blocking1.8.1.5?
Keywords: regression
Attached patch Fix (obsolete) — Splinter Review
This is basically a port to branch of the relevant parts of the fix for bug 337260
Attachment #272127 - Flags: superreview?(jst)
Attachment #272127 - Flags: review?(dveditz)
Attachment #272127 - Flags: approval1.8.1.5?
Attachment #272127 - Flags: approval1.8.0.13?
Blocks: CVE-2007-3089
No longer blocks: 81300
qawanted -- bug 337260 comment 6: "Note to self: test the fix against bug 291745 and bug 292691" might be useful for regression testing (or not).
tried 5 different web mail systems (Gmail, yahoo classic and beta, Zimbra, and Open Webmail) without problems. Don't know who else is likely to use frames, reload them, and expect to reach into it.
This can also affect designMode implementations, see: http://www.mozilla.org/editor/midasdemo/ After a reload, you get a js error and you can't type anymore in the iframe. I would strongly advise to get this patch on the branch...
Also, http://www.squarefree.com/jsenv/ does not work after a reload.
Comment on attachment 272127 [details] [diff] [review] Fix r+ on the patch, clean port (plus branch-interface cruft). I am waiting to give a+ until after I've actually tested the patch just in the rare, rare case bz's success with it depends on some other unnoticed local change.
Attachment #272127 - Flags: review?(dveditz) → review+
Flags: blocking1.8.1.5? → blocking1.8.1.5+
Comment on attachment 272127 [details] [diff] [review] Fix carrying over sr= from the original patch. Patch works on the regressions found so far: approved for the 1.8 branches, a=dveditz
Attachment #272127 - Flags: superreview?(jst)
Attachment #272127 - Flags: superreview+
Attachment #272127 - Flags: approval1.8.1.5?
Attachment #272127 - Flags: approval1.8.1.5+
Attachment #272127 - Flags: approval1.8.0.13?
Attachment #272127 - Flags: approval1.8.0.13+
Comment on attachment 272127 [details] [diff] [review] Fix sr=jst too fwiw
This doesn't include the bits of bug 381300 in it.
Attachment #272127 - Attachment is obsolete: true
I applied the original patch to a tree without 381300, then updated to get the last day of changes including 381300. The final tree that I ran my tests on matched exactly what bz actually checked in after the approvals.
I checked in a mochitest for this.
Flags: in-testsuite+
Oh, this is fixed on both branches as of this morning.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
verified fixed 1.8.1.5. with Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5 ID:2007071317 Works now as expected - also the midasdemo -> adding verified keyword
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: