Closed
Bug 51281
Opened 25 years ago
Closed 25 years ago
Cann not access to the frame in dynamically generated frameset
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
mozilla0.9
People
(Reporter: zhuravok, Assigned: pollmann)
Details
Attachments
(1 file)
|
3.24 KB,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
BuildID: 2000083008
When frameset is dynamically generaed (documnet.write("<html>...</html>")) then
when trying to access to the frames of this frameset - nothing happens - any
frames of frameset can not be accessed and Error appears in JavaScript console
Error: uncaught exception: [Exception... "Failure" code: "-2147467259"
nsresult......
etc.
I think that it will be better when I a user can copy error message in the
clipboard in such cases.
Reproducible: Always
Steps to Reproduce:
1. generate using document.write frameset which contains at least two frames -
both frames should have SRC="about:blank"
2. try to access to any frame right after generation using for example frames
[0].document.
if access to frame will be deffered (for example by using setTimeOut function)
then access to the frame will be successfull.
Expected Results: Access to the frame in the dynamically generated frameset
should working right after document.close() routine.
Reporter: Could you produce an attachment with the code that causes this error
for us?
|
Assignee | |
Comment 3•25 years ago
|
||
|
||
Comment 4•25 years ago
|
||
I can reproduce with Sept 19th build (2000091904).
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
|
||
Comment 5•25 years ago
|
||
Dont know if this relates, but the same exception seems to happen, if one frame
contains a signed jar file which accesses attributes or methods from the second.
UniversalBrowserRead is always granted, btw.
From my personal point of view, thats a dogfood feature, as we heavily depend on
that.
|
|
||
Comment 6•25 years ago
|
||
Sorry, forgot to mention that it once worked with M17 but not any more with M18
and NS6PR3.
|
|
Assignee | |
Comment 8•25 years ago
|
||
This is the same issue as addressed in bug 22681 - the document object is not
attached to the window until the page has finished loading.
*** This bug has been marked as a duplicate of 22681 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
|
||
Updated•7 years ago
|
Product: Core → Core Graveyard
|
||
Updated•7 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•