Closed Bug 35280 Opened 25 years ago Closed 25 years ago

user-focus default value is wrong

Categories

(Core :: CSS Parsing and Computation, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: hyatt, Assigned: pierre)

Details

(Keywords: css3, verifyme)

user-focus is defaulting to a value of "normal", which implies that the control can take the focus. It should be defaulting to "none". I'm not sure what CSS3 says about this, but a default value of normal doesn't make any sense... it's easier to specify the small subset of tags that should get focus than to have to make rules just to deny things from getting focus. This is causing tabbing to be completely screwed up. :)
Keywords: beta2
What does the value "none" mean? It's not in http://www.w3.org/TR/css3-userint#user-focus
Keywords: css3
It was added when peterl talked things over with the CSS3 working group. I'm curious now, though, since it doesn't show up in the spec. We have two "extra" values for user-focus that are required for us to even use it. Normal - The control takes focus when tabbed into or clicked on. None - The control will not take focus. This allows the notion of focusability to be configurable. Anyway, the bug is invalid. It has the right default value, none, although I find the fact that user-focus inherits a bit odd, since container widgets like "select" then have their "option" elements claiming they can be focused. This property doesn't look like it has been though through. Oh well.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Oops, I meant to say Ignore - The control not only doesn't take the focus, but won't cause a blur to occur when an attempt is made to focus it.
Keywords: nsbeta2
Keywords: verifyme
Adding 'verifyme' keyword
I can verify.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.