Moz allows "none" and "ignore" as values for the -moz-user-focus property, which aren't defined by the CSS3 UI WD. And it doesn't allow the "auto" value, which *is* defined by the WD. I'd like to do the following to aid moving bug #97284 along, which doesn't seem to be making much progress: - either fold "none" and "ignore" into one, or preferably remove both in favour of using "-moz-user-input: none" instead. - add support for the "auto" value. - fix bug #138069 I realize that the CSS3 UI WD probably isn't going to go anywhere, but it does exist and would serve as useful documentation for people such as myself who want to do in-browser content editing.
CC'ing hyatt, bzbarsky to get some comments. Adding keywords.
Keywords: css-moz, css3
The user-focus property is not defined at all by the latest public version of the CSS3 UI WD. Reappearance is unlikely, since it breaks the CSS model by allowing properties to influence selectors. The latest version is: http://www.w3.org/TR/2002/WD-css3-ui-20020802/ Note that css3-userint has been superseded by that draft: http://www.w3.org/TR/2002/WD-css3-userint-20020802
17 years ago
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → Future
They are still not in CSS3 UI CR, reappearance is highly unlikely. Is there another draft that is going to define these properties?
Resolving this INVALID since there is no working draft and this should probably be done using contenteditable instead of using CSS.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
Wontfix perhaps, but not invalid, since there was once a WD.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
12 years ago
Assignee: dbaron → nobody
Status: REOPENED → NEW
QA Contact: ian → style-system
It might make sense to change things about this property. However, I don't think an ancient WD is a *reason* to do so, so absent another reason I'm going to mark this as wontfix.
Status: NEW → RESOLVED
Last Resolved: 14 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.