Closed
Bug 207835
Opened 21 years ago
Closed 10 years ago
Mozilla freezes when using fucntionality of this page.
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bobroff, Unassigned)
References
()
Details
(Keywords: hang, testcase)
Attachments
(1 file)
1.47 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 This page is for tracking lost luggage. When a reference number and name are entered into their respective fields and "start query" button is clicked a new window pops up (as it should) but then Mozilla freezes. It works with, ahem, Internet Explorer. The example number/name will demonstrate the problem. Reproducible: Always Steps to Reproduce: 1. Go to http://www.globeground.com/en/pub/services/lostluggage.cfm 2. Fill in the example values given. 3. Click "start query" Actual Results: New window pops up. Nothing fills new window. Mozilla is now "not responding" according to Windows Task Manager. Expected Results: New window should have displayed results of lost baggage search. Using the example values should return saying that it cannot find a valid file for your entry. Using a real value gave me information about a real lost bag (in Internet Explorer), but froze Mozilla.
Comment 1•21 years ago
|
||
same with FB0.6 on Linux!
This page hard locks the browser too: http://www.thebigbikebook.co.uk/order.asp?Page=/clothing.asp§ion=2&subsection=9&Price=0&Start=1&Keyword=&SearchDescription=&Zone=&product=1217
Comment 3•21 years ago
|
||
Confirmed 2003053008 winXP
Comment 4•21 years ago
|
||
Bug occurs in trunk Linux 2003-05-30-08 and in Mozilla 1.0.2
Severity: normal → critical
Comment 5•21 years ago
|
||
This is what all those CPU-cycles are doing: while (popupWindow.frames.length < 2){;}
Comment 6•21 years ago
|
||
Looks like bug 135793
Assignee: general → dom_bugs
Component: Browser-General → DOM Level 0
QA Contact: general → ashishbhatt
Comment 7•17 years ago
|
||
(In reply to comment #6) > Looks like bug 135793 still see this problem, but bug 135793 (which references a related? issue bug 226711) fixed ~2003-11-25
Assignee: general → nobody
QA Contact: ashshbhatt → general
Comment 8•16 years ago
|
||
it now goes to "unresponsive script"
Comment 9•10 years ago
|
||
testcase gone
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•