Closed
Bug 40607
Opened 24 years ago
Closed 24 years ago
Setting javascript location locks the browser
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
People
(Reporter: yori, Assigned: rogerl)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m16) Gecko/20000525 BuildID: 2000052508 Setting the location, location.href, window.location.href, etc. (those are the only variants I tried) locks the browser (I have to kill the process, although I haven't waited for longer than 5 minutes or so). Doesn't seem to matter whether the javascript is typed into the location (as in the submitted URL) or part of a script on the page. Doesn't happen on m15 (I tried switching back to verify). Reproducible: Always Steps to Reproduce: 1. Go to http://slashdot.org/ 2. Type javascript:location.href="/" into the location bar and hit return. Actual Results: Browser hangs; process must be killed. Expected Results: Browser reloads http://slashdot.org/ location.href scripts are sprinkled through web-app I'm working on, largely as a development convenience in JSPs - easier to define a javascript function such as: function reply() { var url = "discussion_create.jsp?<%= baseQuery %>&order=<%= order %>"; url += "&parent=<%= item.getId() %>"; url += "&<%= PSServletUtils.BACK_PARAM %>=<%= URLEncoder.encode( clientUrl + "?" + baseQuery + "&order=" + order + "&item=" + item.getId() ) %>"; location.href = url; } rather than: <a href="discussion_create.jsp?<%= baseQuery %>&order=<%= order %>&parent=<%= item.getId() %>"&<%= PSServletUtils.BACK_PARAM %>=<%= URLEncoder.encode( clientUrl + "?" + baseQuery + "&order=" + order + "&item=" + item.getId() ) %>"> Reply</a>
Comment 1•24 years ago
|
||
dark@c2i.net is right: this is a dup of bug 37463. I have looked at the stack traces on PC/Linux, build 2000052608, and they look the same as expected. *** This bug has been marked as a duplicate of 37463 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•