Please report any other irregularities here.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nb-NO; rv:184.108.40.206) Gecko/20071008 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nb-NO; rv:18.104.22.168) Gecko/20071008 Firefox/22.214.171.124 If the parent window address has another domain name (or even an alias of the same server) and this window tries to access properties of the parent (wich "Same origin policy" doesn't allow) the current window freezes after poping the error console. Must restart firefox to continue. Reproducible: Always Steps to Reproduce: 1.With the included URL: click "open this link". 2.Close the new tab or window. (This calls the onUnload event ) Actual Results: Firefox pops the error console and crashes. Expected Results: Firefox pops the error console and continue to work. This is probably not very a very critical bug. But it sure is annoying, since I the page I'm working on at our test server needs to interface with the old system on another domain. These pages need to modyfy their parent to work, but when it does so when the parent is the test server causes firefox to crash...
Keywords: crash, js1.5, js1.6, js1.7
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Also, give a stacktrace. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Severity: normal → major
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.