User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla 1.4rc1 Dynamically setting iframe src's to a javascript function which itself generates an iframe causes inconsistent rendering. About 20% on 1.4rc1, the correct output is rendered. The other 80% is a blank page. This behavior does not occur with 1.4b1, or any Windows version of Internet Explorer. Reproducible: Always Steps to Reproduce: 1. Load http://zell.best.vwh.net/~zell/moz/ 2. If a blank page is not seen, hit F5 3. Actual Results: A blank page, instead of the correctly rendered page is shown. If rendered correctly, there will be two iframes in the page. The top iframe is the Yahoo! logo, and the bottom iframe is google's home page. Expected Results: Two iframes, one with Yahoo!'s logo, the other with google's home page. This behavior was correct in 1.3, and 1.4b1. Some change in 1.4rc1 broke it.

Still broken in released 1.4. Is this going to be fixed in 1.5?

The JavaScript Console shows two errors: Error: uncaught exception: Permission denied to get property Window.step_one Error: uncaught exception: Permission denied to get property Window.step_three Is there a problem with the JavaScript in the page?

The javascript errors seem related to the resurrected(?) bug: http://bugzilla.mozilla.org/show_bug.cgi?id=123696 I am using hard reloads to get around this. The blank page still shows up approximately 20% of the time.

Sounds like a DOM bug to me (the JS errors keep the JS from being executed at all...)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050402 Windows XP Home Edition Service Pack 2 + All current Patches Shockwave Flash 7.0 r19 Java Plug-in 1.5.0_02 for Netscape Navigator Reload (F5) Still produces a blank page, JS console still shows errors cited in Comment 2 above.

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/

Still find the following errors in the JavaScript console after a soft reload: Error: uncaught exception: Permission denied to get property Window.step_one Error: uncaught exception: Permission denied to get property Window.step_three Windows XP, Firefox 1.5 Beta 1

No testcase, no steps to reproduce without said testcase. Resolving incomplete until there's a way to do something else here.