Closed
Bug 462375
Opened 17 years ago
Closed 17 years ago
setInterval/setTimeout Not Working From Within iFrames
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: remacgregor, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
If the page within a iframe contains Javascript that calls setInterval or setTimeout, the setInterval/setTimeout calls are ignored. This occurs in FF 3 (Win), but not in FF 3 (Mac) or any other browser.
Reproducible: Always
Steps to Reproduce:
1. Create a page with an iframe (the parent).
2. In the source page (the child) for the iframe, include Javascript like setInterval("alert('hi')", 100);, for example.
3. Load the parent page and watch as FF3 (Win) fails to execute alert('hi');.
Actual Results:
Nothing happens.
Expected Results:
alert('hi');
Comment 1•17 years ago
|
||
Anything in the error console?
Comment 2•17 years ago
|
||
Works fine for me, do you have a simple testcase that fails?
Comment 3•17 years ago
|
||
Unable to reproduce Ubuntu build:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3
Unable to reproduce Windows build:
Mozilla/5.0 (Windows; U; Windows NT 6.0; da; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Comment 4•17 years ago
|
||
No demonstration of an actual problem here, closing as incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
Comment 5•5 years ago
|
||
Digging this one out the crypt here.
It seems the bug happens when you have the Developer Tools window open and step through the code in the iframe.
No errors are triggered but the function passed to setInterval does not run.
Reloading the iframe in another tab fixes the error, as does restarting Firefox.
Just posting this here in case someone else hits this bug and wastes time like I did.
You need to log in
before you can comment on or make changes to this bug.
Description
•