Closed
Bug 224720
Opened 22 years ago
Closed 20 years ago
strange behaviour while invoking frme.contentDocument.write in frmeset.onload
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: rook, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; pl-PL; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; pl-PL; rv:1.4) Gecko/20030624
on loading the HTML file below (locally) Mozilla leaves the cursor "arrow and
hourglass" after finishing. Upon reload Mozilla locks up. After another reload
only tow of 3 frames are correctly rendered. Everything is fine after another
reload.
<head>
<script language="javascript">
function abc()
{
var fr = document.getElementsByTagName("FRAME");
for (i = 0; i < fr.length; i++)
{
var aa = fr[i].contentDocument
aa.write(fr[i].id);
}
}
</script>
</head>
<frameset cols="20%,*" onload="abc()">
<frame id="lmenu"/>
<frameset rows="20%,*">
<frame id="tmenu"/>
<frame id="bd"/>
</frameset>
</frameset>
</html>
Reproducible: Sometimes
Steps to Reproduce:
1.
2.
3.
|
||
Comment 1•22 years ago
|
||
> on loading the HTML file below (locally) Mozilla leaves the cursor "arrow and
> hourglass" after finishing.
That's correct, since the subdocuments are still loading (document.open() has
been called, but not document.close())
|
|
Reporter | |
Comment 2•22 years ago
|
||
The frames here have no src, hence they are not loading anything. Furthermore I
wouldn't call a lockup a "correct behaviour". The fact that Mozilla behaves
differently between consequent reloads is IMHO far from being correct.
If the problem virtually lies in unfinished document loading then maybe an
exception should be thrown... ??
|
|
Reporter | |
Comment 3•22 years ago
|
||
Here's the villain that confuses my beloved Mozilla ;)
|
|
||
Comment 4•22 years ago
|
||
Confirmed with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b)
Gecko/20040421
I was able to reproduce the bug with the previous attachment. I built a
simplified attachment that exhibits the same problem.
Behavior:
1st load of the page:
It looks like it loads correctly except that the hourglass doesn't go away.
hit Reload.
2nd load:
It looks like it is taking forever for the page to load. Note: abc() hasn't
been called yet.
hit Stop.
abc() is called, but the framed page is "null" so it can't be written to.
hit Reload
3rd load (all all subsequent):
it looks like it loads correctly, but the javascript console shows the
following error:
Security Error: Content at
wyciwyg://53/file:///C:/Documents%20and%20Settings/Name/Desktop/hg2.htm may not
load or link to file:///C:/Documents%20and%20Settings/Name/Desktop/hg2.htm.
|
||
Updated•21 years ago
|
Product: Browser → Seamonkey
|
|
||
Comment 5•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
|
|
||
Comment 6•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•