canmove, Confirmed users
2,675
edits
Tantek-Mozilla-Projects: Difference between revisions
→Styling HTML5 forms elements: note related bug 457801, placeholder attribute, :placeholder pseudoclass
(→CSS3 UI: next-actions for producing a minimal test suite, new LCWD, CR, and taking it to PR) |
(→Styling HTML5 forms elements: note related bug 457801, placeholder attribute, :placeholder pseudoclass) |
||
| Line 35: | Line 35: | ||
==== Styling HTML5 forms elements ==== | ==== Styling HTML5 forms elements ==== | ||
We need to define how Forms must be styled, and to synchronize our work with the W3C. | |||
Working with Mounir Lamouri on this: [[User:Mounir.lamouri/HTML5_Forms]] | |||
Each [[HTML5]] form element must be complete to the following criteria: | Each [[HTML5]] form element must be complete to the following criteria: | ||
| Line 54: | Line 56: | ||
* ability to select specific "pieces" of any compound/composite form control for styling | * ability to select specific "pieces" of any compound/composite form control for styling | ||
** feeds into requirements for CSS pseudo-elements | ** feeds into requirements for CSS pseudo-elements | ||
** consider existing UI pseudo-elements | ** consider existing UI pseudo-elements | ||
*** [http://www.w3.org/TR/css3-ui/#pseudo-elements ::value ::choices ::repeat-item ::repeat-index] | *** [http://www.w3.org/TR/css3-ui/#pseudo-elements ::value ::choices ::repeat-item ::repeat-index] | ||
**** ::value in particular can be used for selecting/styling placeholder text (see [https://bugzilla.mozilla.org/show_bug.cgi?id=457801#c25 bug 457801 comment 25]). | |||
* ability to select specific "states" of any form control (may require ability to select states of specific pieces as well - that will be a challenge though as pseudo-elements themselves cannot have pseudo-classes in CSS) | * ability to select specific "states" of any form control (may require ability to select states of specific pieces as well - that will be a challenge though as pseudo-elements themselves cannot have pseudo-classes in CSS) | ||
** existing [http://www.w3.org/TR/css3-selectors/#UIstates Selectors UI pseudo-classes], and some notes on [http://www.w3.org/TR/html5/interactive-elements.html#pseudo-classes how HTML5 DOM property states trigger these pseudo-classes] | ** existing [http://www.w3.org/TR/css3-selectors/#UIstates Selectors UI pseudo-classes], and some notes on [http://www.w3.org/TR/html5/interactive-elements.html#pseudo-classes how HTML5 DOM property states trigger these pseudo-classes] | ||
| Line 68: | Line 71: | ||
*** :required and :optional - [http://www.w3.org/TR/html5/interactive-elements.html#selector-required see HTML5 description of being required / required attribute] | *** :required and :optional - [http://www.w3.org/TR/html5/interactive-elements.html#selector-required see HTML5 description of being required / required attribute] | ||
*** :read-only and :read-write - [http://www.w3.org/TR/html5/interactive-elements.html#selector-read-only see HTML5 description of read-only vs read-write elements]. | *** :read-only and :read-write - [http://www.w3.org/TR/html5/interactive-elements.html#selector-read-only see HTML5 description of read-only vs read-write elements]. | ||
** additional pseudo-selectors as needed for states/portions included in HTML5 forms elements features | |||
*** "placeholder" attribute - needs a new :-moz-placeholder pseudo-class ([https://bugzilla.mozilla.org/show_bug.cgi?id=457801 bug 457801]) | |||
**** :placeholder pseudo-class needs to be proposed for CSS3.1 UI/Selectors. | |||
* typography | * typography | ||
** font properties | ** font properties | ||