45485 - css :focus class not properly reset/removed if switching focus away

Status: VERIFIED DUPLICATE of bug 54820

(Core :: Layout: Form Controls, defect, P4)

Description

[Matthias Kerkhoff]

From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (WinNT; U)
BuildID:    2000071320

If a form control A has the focus and it's switch away to a control B in another 
frame, the control A still retains its membership in the :focus class.

Reproducible: Always
Steps to Reproduce:
1. Create to frames with forms and controls in them
2. Set a :focus property (I've used background-color)
3. switch the focus between the controls.

Actual Results:  The resulting visual representation indicates, that one control 
per frame is ready for input. 		

Expected Results:  Only one control should be in :focus. Lets assume, the 
controls are text-inputs. 
The css-spec states "The :focus pseudo-class applies while an element has the 
focus (accepts keyboard events or other forms of text input).". 
Not only that only one control has the focus, it's also impossible for the user 
to enter text in more than one control (w/o switching between the frames). 
Furthermore it's inconsistent with the event model. Switching focus from control 
A to B across frame borders _will_ generate DOM/JavaScript focus and blur 
events.

As always, this is just an opinion and it may be wrong.

Comment 1

[Matthias Kerkhoff]

Some more examples...
Szenario: Two frames, one with two groups of checkboxes, one with edit controls.
1. Check one of the checkboxes of group 1
2. Move the mouse away from it - it will get the focus outline
3. Move the mouse over the checkbox again (it will come into :hover)
4. Move the mouse away from it - it be/retain in :focus
5. Now click in one of the edit controls (the checkbox will keep its focus 
outline
6. Move the mouse over the selected checkbox, don't click. It will now loose 
:focus. (ERROR, why now?)

Comment 2

[Matthias Kerkhoff]

Oops. Commited too early. 
The reverse szenario leads to the same problem (edit controls also loose :focus, 
if mouse is moved over them after a similar procedure as described above).

Comment 3

[rods (gone)]

Chris, this seems like it would be yours.

Comment 4

[Matthias Kerkhoff]

May be related to #42553.

Comment 5

[saari (gone)]

correctness, nominating nsbeta3

Comment 6

[Peter Trudelle]

nsbeta3-, not a big problem for NS6 apps, but should have for standards.  low
priority, helpwanted.

Comment 7

[bsharma]

Updating QA contact.

Comment 8

[saari (gone)]

mozilla 1.0

Comment 9

[Vladimir Ermakov]

QA Contact Update

Comment 10

[joki (gone)]

*** This bug has been marked as a duplicate of 54820 ***

Comment 11

[Vladimir Ermakov]

verifying duplicate, this is fixed...