Closed
Bug 161456
Opened 23 years ago
Closed 2 months ago
Hangs if text is replaced by space
Categories
(Core :: DOM: Events, defect, P4)
Core
DOM: Events
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: glashoff, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
1.15 KB,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722
BuildID: 2002072204
In the page at http://glashoff.net/bugzilla/testempty.html the browser hangs
after clicking on the text in the top of the page.
Reproducible: Always
Steps to Reproduce:
1.Load the page at http://glashoff.net/bugzilla/testempty.html
2.Click on the text at the top of the page.
Actual Results: The browser hangs which can be recognized by trying the
MOUSEOVER - effect on the text at the bottom of the page which has just been
added for that purpose.
Expected Results: Mozilla should have worked as usual, .f.i. the mouseover -
effect described above should work on the text on the bottom.
The problem is the following command:
document.getElementById('t1').firstChild.nodeValue=''
where there is "nothing" or space as value.
This problem is not present in the WINDOWS-Version.
Comment 1•23 years ago
|
||
http://glashoff.net/bugzilla/testempty.html gives me a 404. What is the correct URL?
Comment 2•23 years ago
|
||
URL works now.
Browser doesn't completely hang, but selecting text on the page becomes
impossible and the mouseover/mouseout isn't executed anymore. Also, after
clicking in the URL bar, you cannot focus the page (when you clicking on the
page, the URL bar is still selected).
After a reload text selecting, mouseover/mouseout and focus switching work again.
Confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•23 years ago
|
||
See it too (2002080419, WinNT). Problem disappears when you remove #t1
selector's "position:absolute".
-> normal
Severity: critical → normal
Comment 4•23 years ago
|
||
Just in case the link goes dead
Comment 6•22 years ago
|
||
The hang is not freesing the browser, only events fired at the particular page,
you can still navigate to a different page, or have this one reloaded. Why would
making a node empty during an event block other events from firing... I tried to
remove child instead of setting value to '', and this did not cause any
problems, so it appears the only time this occurs is if value is set to ''.
Priority: -- → P4
Updated•16 years ago
|
Assignee: joki → nobody
QA Contact: vladimire → events
Updated•3 years ago
|
Severity: normal → S3
Comment 7•2 months ago
|
||
test case in comment 4 works for me, Fx 137,
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•