Closed
Bug 29515
Opened 25 years ago
Closed 25 years ago
Moving mouse over links at abcnews.com freezes browser
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: shrir, Assigned: joki)
References
()
Details
(Keywords: crash, top100, Whiteboard: [PDT+] w/b minus on 3/10)
Attachments
(4 files)
Pls reassign to correct component if incorrect. Thnx ! I see this on today's commercial build on all platforms (2000022808m15) To recreate the problem, please do the following: 1. Install and launch hte browser 2. Type the url 'www.abcnews.com' in the Locationbox and press ENTER 3. Observe the page loads up 4. Now just move the mouse over the links in the left frame( with blue background). 5. Observe that the browser freezes and no links work.
Comment 1•25 years ago
|
||
Same here - with: 2000022908, win98 A cut from the code of this page in the area of the problem: http://www.geckonnection.com/testcases/testlinks.html - start moving the mouse slowly over the links - then, move DeSpErAtElY! over the links and see that performance goes down...
Comment 2•25 years ago
|
||
New testcase --> http://www.geckonnection.com/testcases/testlinks1.html Note: NOT FREEZING anymore here (2000022908), I cut the <font....> tags from the file.
Reporter | ||
Comment 3•25 years ago
|
||
Yup, I see this too..
Comment 4•25 years ago
|
||
Marking crash and top100 and beta1 and m14. Setting severity critical. Freezing/crashing on home page of a top100 site is serious.
Assignee | ||
Comment 6•25 years ago
|
||
Hmm. Trying to decide if this is a dupe of 18539 that we closed a long time ago. Its still abcnews but that test case still seems to work. Useful info though.
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•25 years ago
|
||
Assignee | ||
Comment 10•25 years ago
|
||
Okay weird, the test case at the bottom works (as in fails) for me on the server but no locally. Fun. Gonna put up a smaller testcase to check this out.
Assignee | ||
Comment 11•25 years ago
|
||
Assignee | ||
Comment 12•25 years ago
|
||
Okay, got a fix. Need to get a review and checkin authorization
Whiteboard: [PDT+] w/b minus on 3/10 → [PDT+] fix in hand, w/b minus on 3/10
Assignee | ||
Comment 13•25 years ago
|
||
Harish, by the way. I found that the parser is most definitely not to blame here. It's definitely a lower level frame issue. I managed to create identical content trees, both of which recursively nested the content nodes, one of which showed the freezing problem, one of which did not.
If you're curious, this seems to work OK on my current tree (with all my event targetting changes that I'm waiting until after beta1 to check in). Not that that will help much...
Assignee | ||
Comment 15•25 years ago
|
||
*** Bug 24352 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 16•25 years ago
|
||
Okay, this should be much better now.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] fix in hand, w/b minus on 3/10 → [PDT+] w/b minus on 3/10
Comment 17•25 years ago
|
||
Verified WinNT, Win98: 2000-03-13-18-M15-nb1b Mac: 2000-03-13-17-M15-nb1b Linux: build not working - will verify later
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•