Differences

This shows you the differences between two versions of the page.

--- spec:css4-ui [2014/11/19 09:18] – [more selectors] note ::value has a Mozilla implementation bug tantek
+++ spec:css4-ui [2016/05/10 13:08] – [more selectors] removed :playing and :paused as we resolved today to add them to Selectors hober
@@ Line 19: / Line 19: @@
   * new 'cursor' values:
     * 'auto-hide' - being added to WebKit as [[https://bugs.webkit.org/show_bug.cgi?id=107601|-webkit-auto-hide]], see [[http://lists.w3.org/Archives/Public/www-style/2013Feb/0194.html|this www-style thread]]
-    * 'grab' - supported by Mozilla as [[https://developer.mozilla.org/en/CSS/-moz-grab|-moz-grab]]
-    * 'grabbing' - supported by Mozilla as [[https://developer.mozilla.org/En/CSS/-moz-grabbing|-moz-grabbing]]
     * see [[https://developer.mozilla.org/en/CSS/cursor#Mozilla_extensions|CSS cursor Mozilla extensions]] for more
     * consider more from: http://www.gtalbot.org/DHTMLSection/Cursors.html#Proprietary
@@ Line 75: / Line 73: @@
 ==== more selectors ====
+  * ::selection - moved from CSS3-UI - more details/issues/links collected [https://www.w3.org/wiki/CSS3-UI#Issue_30 W3C wiki for now].
   * ::placeholder pseudo-element for the placeholder content inside an input element with a placeholder attribute.
     * There's an empty documentation page for [[https://developer.mozilla.org/en-US/docs/CSS/::-moz-placeholder|::-moz-placeholder]] which is implemented as of Firefox 19.
   * :placeholder-shown pseudo-class for when an input element is in the state of showing its placeholder text
     * See [[ideas/placeholder-styling|placeholder styling]] for more detailed exploration of :placeholder vs. ::placeholder (or potentially both).
-    * [[https://developer.mozilla.org/en/CSS/%3a-moz-placeholder|:-moz-placeholder]] documentation
+    * [[https://developer.mozilla.org/en/CSS/%3a-moz-placeholder|:-moz-placeholder]] documentation ([[https://developer.mozilla.org/en-US/docs/Web/CSS/::-moz-placeholder|deprecated in FF19]])
     * [[https://bugzilla.mozilla.org/show_bug.cgi?id=457801|Mozilla bug 457801]]:  Implement -moz-placeholder pseudo-class - big long discussion of pseudo-class vs. pseudo-element etc.
   * [[https://wiki.mozilla.org/CSS/:autofill|:autofill]] pseudo-class for when an input element is in the state of showing an autofilled value. Related implementer bugs (not yet implemented) :
@@ Line 95: / Line 94: @@
   * [[http://lists.w3.org/Archives/Public/www-style/2011Nov/0705.html|::backdrop-of(selector)]] - a pseudo-element that matches the backdrop of a fullscreened element, a modal dialog, or other platform features with similar needs.
   * ::value - postponed from CSS3-UI, however there is a [https://bugzilla.mozilla.org/show_bug.cgi?id=648643 Mozilla implementation bug 648643] for it.
+  * :has-focus pseudo-class - see [http://lists.w3.org/Archives/Public/www-style/2014Nov/0271.html proposal] and [http://lists.w3.org/Archives/Public/www-style/2014Nov/thread.html#msg271 subsequent thread]
 ==== pointer-events ====
 Moved from CSS3-UI editor's draft because it was the top source of issues for the 2nd CSS3-UI LCWD, and because it requires documenting previously undocumented web platform hit-testing model.
@@ Line 170: / Line 170: @@
   * http://www.w3.org/wiki/User:Tantekelik/CR-css3-ui-20040511-appearance
+Suggestion that more values than just none and auto are useful:
+http://www.w3.org/mid/5127EB91.7000002@inkedblade.net
+This has now been drafted here: http://dev.w3.org/csswg/css-ui-4/#appearance-switching
 ==== nav properties ====
 nav-index:
@@ Line 231: / Line 236: @@
 Spec Status:
-  * not in any current draft.
+  * draft here: http://dev.w3.org/csswg/css-ui-4/#content-selection
-Last publication:
+====== css4-ui issues list ======
-  * http://www.w3.org/TR/2000/WD-css3-userint-20000216#user-select
-Issues:
+===== Current Issues =====
-  * 'all' vs. 'atomic' value
-    * Gecko implementation of the 'all' value does not reflect last specified definition (2000).
-    * WebKit wants a 'atomic' value that acts as 'all' was specified in 2000.
-    * Might be possible to get Gecko to change its 'all' behavior to as specified and avoid introducing a new 'atomic' value.
-  * 'none' vs. '-moz-none' value
-    * Gecko 'none' vs '-moz-none' differences: http://blogs.telerik.com/blogs/07-05-21/-moz-user-select--moz-none.aspx
-    * Gecko implementation of '-moz-none' (but not 'none') is like WebKit/IE/Opera's 'none' value.
-      * related: [[https://bugzilla.mozilla.org/show_bug.cgi?id=816298|Bugzilla 816298]]: Change "-moz-user-select:none" to behave like WebKit, IE, and Opera (and "-moz-user-select:-moz-none")
-For CSS4-UI:
+The editor's draft is here:
-  * Minimum: spec the interoperable values among existing implementations (excluding 'all')
+  * http://dev.w3.org/csswg/css-ui-4/
-  * Possibly: minimum plus keep 'all' as specified, and get Gecko fixed to be compliant
-  * Maximum: spec all values, including 'toggle' and 'elements' and file bugs accordingly with existing implementations to get those values implemented.
-====== css4-ui issues list ======
-===== Current Issues =====
-There is no editor's draft of CSS4-UI yet - so there's nothing to have issues against!
-The editor's draft will eventually be here:
+For now, issues are primarily tracked inline, although this wiki contains relevant information that predates the creation of the draft.
-  * http://dev.w3.org/csswg/css4-ui/
 ====== Issues moved from css3-ui ======