Closed
Bug 60888
Opened 24 years ago
Closed 24 years ago
Executing javascript: script as an href freezes the app
Categories
(Core :: Networking, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla0.8
People
(Reporter: racham, Assigned: danm.moz)
References
Details
Attachments
(1 file)
227 bytes,
text/html
|
Details |
I have a small utility script that I used as one of the personal bookmarks. It is used to findout phone numbers. That script contains javascript: syntax. I made a simple html file out of that and hooked that script to a hyper-link in that file. I will attach that file in the next update. When I click on that link, the app simply freezes. I have to kill it using the Task Manager. This got to be a problem either in processing the javascript: script associated with href or a context issue.
Summary: Excuting javascript: script as an href freezes the app → Executing javascript: script as an href freezes the app
Note : If I had any other window open at that time, clicking on that window is somehow triggering the request to process the javascript: script.
Comment 3•24 years ago
|
||
I'm betting you are just seeing a problem with the prompt dialog. I note that this was reported as a problem with yesterday's builds... news://news.mozilla.org/20001120123038.E22735%40netscape.com Have you really narrowed it down to the javascript: being processed? Maybe you can try javascript:dump('foo\n'); and see if that runs or not.
Same problem as bug 55460 (see a comment within from jband, 13 October) and a few others. There's a general underlying problem causing a lot of similar issues. See especially the discussion going on in bug 56337, where the problem has been identified and solutions are being considered. I'm marking this bug as dependent on that one, though it could also reasonably be called a duplicate. I've verified this by trying this bug with and without the changes to nsThread.cpp outlined in 56337. It's the same problem.
Depends on: 56337
Comment 5•24 years ago
|
||
Why is this a networking bug? Can someone please give it a more appropriate home?
It's more a fixed bug than a networking bug. This was more fallout from worker threads' occasionally going AWOL.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla0.8
danm: if this isn't networking, can you fix the component and default qa for me? TIA.
You need to log in
before you can comment on or make changes to this bug.
Description
•