Differences

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

--- spec:css4-ui [2014/12/09 15:48] – external edit 127.0.0.1
+++ spec:css4-ui [2015/08/25 05:59] – re-add media play state pseudos 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 80: / Line 78: @@
   * :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 89: / Line 87: @@
   * [[https://developer.mozilla.org/en-US/docs/CSS/:-moz-suppressed|:suppressed]] for elements representing images that were not loaded because loading images from that site has been blocked.
   * [[https://developer.mozilla.org/en-US/docs/CSS/:-moz-loading|:loading]] for elements none of which can be displayed because they have not started loading, such as images that haven't started to arrive yet.  Note that images that are in the process of loading are not matched by this pseudo-class.
+  * :playing, :paused on media elements, for styling custom media controls
   * [[https://developer.mozilla.org/en/CSS/%3a%3a-moz-progress-bar|::progress-bar]] pseudo-element for selecting and styling the area of an HTML progress element that represents the amount of progress that has happened so far. This lets you, for example, change the color of progress bars.
   *  :valid-drop-zone, :invalid-drop-zone - a drop-zone (as Mozilla implements [[https://developer.mozilla.org/en/CSS/:-moz-drag-over|:-moz-drag-over]]) that is valid/invalid.
@@ Line 175: / Line 174: @@
 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 236: / Line 237: @@
 Spec Status:
-  * not in any current draft.
+  * draft here: http://dev.w3.org/csswg/css-ui-4/#content-selection
-Last publication:
-  * http://www.w3.org/TR/2000/WD-css3-userint-20000216#user-select
-Issues:
+====== css4-ui issues list ======
-  * 'all' vs. 'atomic' value (resolved)
-    * 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.
-    * As of FF 33, the difference in behavior (non atomic select when doing keyboard selection) appears to be gone.
-  * 'none' vs. '-moz-none' value (Resolved)
-    * 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")
-    * From Firefox 21, '-moz-none' and 'none' in Firefox do the same as 'none' in other browsers
-For CSS4-UI:
+===== Current Issues =====
-  * Minimum: spec the interoperable values among existing implementations (excluding 'all')
-  * 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.
-=====
+The editor's draft is here:
-= css4-ui issues list ======
+  * http://dev.w3.org/csswg/css-ui-4/
-=====
- 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 ======
-= Issues moved from css3-ui ======
 The following issues were removed form css3-ui's issue list, as they pertain to features that were removed from that document. They are collected here, as these features may be reintroduced in css4-ui, and the issues would then still be relevant.
-====
+==== Issue 4 ====
-Issue 4 ====
   ; Summary : computed value of 'pointer-events' vs initial value vs SVG vs CSS3-UI conflict. A quick test shows that IE9 and Opera return 'visiblePainted', while WebKit and Firefox return 'auto'.
   ; Raised by: Erik Dahlstrom