Non-standard
This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
The -moz-user-focus
CSS property is used to indicate whether an element can have the focus.
/* Keyword values */ -moz-user-focus: normal; -moz-user-focus: ignore; /* Global values */ -moz-user-focus: inherit; -moz-user-focus: initial; -moz-user-focus: unset;
By setting its value to ignore
, you can disable focusing the element, which means that the user will not be able to activate the element. The element will be skipped in the tab sequence.
Initial value | none |
---|---|
Applies to | all elements |
Inherited | no |
Media | interactive |
Computed value | as specified |
Animation type | discrete |
Canonical order | the unique non-ambiguous order defined by the formal grammar |
textbox
elements, because the textbox
itself never takes focus. Instead, XBL creates an anonymous HTML <input>
element inside the textbox
, and that element is what receives focus. You can stop the textbox
from taking keyboard focus by setting its tab index to -1
, and from taking mouse focus by preventing the default action of mousedown
events.Syntax
Values
ignore
- The element does not accept the keyboard focus and will be skipped in the tab order.
normal
- The element can accept the keyboard focus.
select-after
- ?
select-before
- ?
select-menu
- ?
select-same
- ?
select-all
- ?
none
- ?
Formal syntax
ignore | normal | select-after | select-before | select-menu | select-same | select-all | none
Example
HTML
<input class="ignored" value="The user cannot focus on this element.">
CSS
.ignored { -moz-user-focus: ignore; }
Specifications
This property is not part of any specification. A similar property, user-focus
, was proposed in early drafts of a predecessor of the CSS3 UI specification, but was rejected by the working group.
Browser compatibility
We're converting our compatibility data into a machine-readable JSON format. This compatibility table still uses the old format, because we haven't yet converted the data it contains. Find out how you can help!
Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|
Basic support | No support | (Yes) | No support | No support | No support |
Feature | Android | Chrome for Android | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
---|---|---|---|---|---|---|
Basic support | No support | No support | ? | No support | No support | No support |