Closed Bug 302665 Opened 19 years ago Closed 16 years ago

controls lost after this.parentNode.style.display='none'; return false;

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: pbspam, Unassigned)

Details

(Whiteboard: dupme)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

After you click on the link rendered by the following code, you lose basically
all control of the current Firefox window (no mouse wheel scrolling, no keyboard
arrow scrolling, no keyboard shortcuts like Ctrl+T, Ctrl+N, Alt+D, Ctrl+R...)
until you click with the mouse on the document body. (Both JavaScript lines are
required for the bug, but the <BR>'s are just for page lengthening.)

<html><body>

<div id="showcomments">
<a href="something" onclick="this.parentNode.style.display='none'; return
false;">click here</a>
</div>

<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>

</body></html>

Reproducible: Always

Steps to Reproduce:
1. Copy the code in Details to a html file.
2. Open it using Firefox.
3. Click on the link.
Actual Results:  
After the link disappears, keyboard controls and mousewheel scrolling is lost
until I click somewhere in the document body.

Expected Results:  
After the link disappears, all controls remain accessible.
A remark: the problem is not with href="something". The bug is from an actual
web page where href contained a valid link. However, if href is completely
removed, the displayed text is not a link any more.
this does not have anything to do with href. It seems the focus is not switched
to the next element when display:none is applied. This is WFM in Deer Park alpha
2 btot not in FF 1.0.6  am guessing it a dup but I can not find teh dup bug.
Whiteboard: dupme dupme
Whiteboard: dupme dupme → dupme
Version: unspecified → 1.0 Branch
wfm per comment 2
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.