Canmove, confirm
2,678
edits
Changes
update a few CSS-UI related tasks
* <code><input type="month-day"></code> - based on <code><time></code> element use case research
===== CSS3 CSS UI appearance values =====<span id="CSS3_UI_appearance_values"> </span>
From [http://www.w3.org/TR/css3-ui/#appearance-val CSS3 UI 5.1. Appearance values]:
* '''text-overflow'''
** create an implementer FAQ on the CSS WG wiki re: text-overflow accordingly
* ''':indeterminate''' - add an example using [https://developer.mozilla.org/en/HTML/Element/progress HTML5 progress element] and with input type=checkbox with DOM property set to indeterminate deliberately per [https://developer.mozilla.org/en/CSS/%3aindeterminate devmo :indeterminate example]
* '''resolve issues'''. resolve/apply proposals from issues list: http://wiki.csswg.org/spec/css3-ui
* '''implementation documentation'''. document claims of existing implementations
**** [https://developer.mozilla.org/en/CSS/-moz-copy copy] - verify works w/o prefix.
*** [https://developer.mozilla.org/en/CSS/outline-offset outline-offset] -
*** Remaining related Firefox bugs/development tasks (stub/incomplete). For each of these, figure out who is the right Mozilla developer to work on this and then work with to understand what it will take to get it implemented:**** cursor / border-radius interaction bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=595652 595652]***** if/when fixed, add that detail to spec**** cursor on root element applying to viewport: [https://bugzilla.mozilla.org/show_bug.cgi?id=568450 568450] ***** if/when fixed, add that detail to spec**** icon support: http://www.w3.org/TR/css3-ui/#element***** 'icon' property***** 'content:icon' value**** box-sizing prefix drop: https://bugzilla.mozilla.org/show_bug.cgi?id=243412**** ... ** Internet Explorer 8 + CSS3 UI support - ??? (expect email from johnjan @ MS)
** IE5/Mac CSS3 UI support - ???
* document actual implementation results
** incrementally draft new CSS3-UI CR draft accordingly
* wait for new edit CSS3 -UI LCWD last-call period CR draft accordingly that is ready for PR** reduce feature set down to endwhat's been implemented in more than one browser, or in one browser and imminently expected in another browser. mark at risk anything that is not interop in 2+ browser per above tests.
* write publish CSS3-UI Selectors LCWD - with features with at least one implementation, any CR2 with less than 2 implementations, mark at risk.minimal test suite and results
* edit CSS3-if necessary, write new UI CR Selectors FPWD editors draft accordingly that is ready for PR** reduce feature set down with all new UI selectors (consider limiting to what's been implemented in more those with at least one implementation, any with less than one browser2 implementations, or in one browser and imminently expected in another browser.mark at risk up front)
* WG processes for taking it to PR
==== CSS4 UI ====
*** stuff from CSS3 UI CR that only had one implementation (that we believe is worthy of standardizing, or at least one other implementer expresses interest on)
*** stuff from and related to previous CSS3 UI drafts that's been reraised
**** 'appearance' (especially 'none' value)
***** consider updated ''appearance'' property with updated set of native UI controls from Alex Faaborg and incorporating analysis in the [[#CSS_UI_appearance_values|CSS UI appearance values]] section above.
**** 'user-input'
**** 'user-focus'
**** both suggested by: [http://lists.w3.org/Archives/Public/www-style/2010Dec/0383.html www-style: Re: Implementing contentEditable in CSS3 UI]
*** more "overflow" extensions: http://wiki.csswg.org/spec/css3-overflow
Additional CSS3 UI related features in Mozilla to investigate:
* [https://developer.mozilla.org/en/CSS/-moz-user-focus -moz-user-focus]
==== CSS3 Element ====
====== box-sizing padding-box ======
* add ''box-sizing: padding-box'' per Mozilla definitions
===== CSS3 UI LCWD2 =====
publish new CSS3 UI LCWD with new at-risk features based on above implementation evidence (or imminent implementation - kept at risk), and all known outstanding issues resolved. (back to last call because we added features after the CR, and moved some previous features to at-risk).
