Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
spec:css4-ui [2014/11/26 07:46] – [text-overflow start end values] florianspec:css4-ui [2023/07/06 14:09] (current) – Added reference to GitHub issue for middle cropping SebastianZ
Line 19: Line 19:
   * new 'cursor' values:   * 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]]     * '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     * 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     * 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   * :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).      * 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://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) :   * [[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 129: Line 127:
 Some mechanism to control ellipsing of text by allowing it to be ellipsed "in the middle" (somehow). See also other related text-overflow features dropped from CSS3. Some mechanism to control ellipsing of text by allowing it to be ellipsed "in the middle" (somehow). See also other related text-overflow features dropped from CSS3.
  
-See emails:+See emails and GitHub issue:
   * http://www.w3.org/mid/CANTc86Wi3K1JHo0XJuWMVC0vCOBM+1D2+=ad=7=S0ofaD_jdAg@mail.gmail.com   * http://www.w3.org/mid/CANTc86Wi3K1JHo0XJuWMVC0vCOBM+1D2+=ad=7=S0ofaD_jdAg@mail.gmail.com
   * http://www.w3.org/mid/CAERejNaV+5ZCu9b9yX7dKWPjq0rfVGH4DgxST6NZ-xVD3PD=QQ@mail.gmail.com   * http://www.w3.org/mid/CAERejNaV+5ZCu9b9yX7dKWPjq0rfVGH4DgxST6NZ-xVD3PD=QQ@mail.gmail.com
 +  * https://github.com/w3c/csswg-drafts/issues/3937
 ==== touch-action ==== ==== touch-action ====
 The Pointer Events WD introduced a "touch-action" property. The Pointer Events WD introduced a "touch-action" property.
Line 175: Line 173:
 Suggestion that more values than just none and auto are useful: Suggestion that more values than just none and auto are useful:
 http://www.w3.org/mid/5127EB91.7000002@inkedblade.net 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 properties ====
 nav-index: nav-index:
Line 236: Line 236:
  
 Spec Status: 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'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. 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'.   ; 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   ; Raised by: Erik Dahlstrom
 
spec/css4-ui.1417016787.txt.gz · Last modified: 2014/12/09 15:48 (external edit)
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki