canmove, Confirmed users
2,675
edits
Tantek-Mozilla-Projects: Difference between revisions
→Styling HTML5 forms elements: consider existing pseudo-elements
(→Styling HTML5 forms elements: more pseudo-class details) |
(→Styling HTML5 forms elements: consider existing pseudo-elements) |
||
| Line 23: | Line 23: | ||
* 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 | ||
** existing pseudo-elements | ** consider existing UI pseudo-elements - do any of these make sense for new HTML5 input types? | ||
** | *** [http://www.w3.org/TR/css3-ui/#pseudo-elements ::value ::choices ::repeat-item ::repeat-index] | ||
* 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] | ||