Canmove, confirm
2,698
edits
Changes
→Styling HTML5 forms elements: generalized to UI elements, note possible need for additional pseudo-elements, e.g. from vendor prefixed examples
The theory is that by addressing that first that it will become more obvious which specific real-world rich interfaces fall into the second cluster, and therefore we can design for that second cluster based on those specific interfaces.
==== Styling HTML5 forms UI elements ====We need to define how Forms must and other UI elements can be styled, and to synchronize our work with the W3C.
Working with Mounir Lamouri on this: [[User:Mounir.lamouri/HTML5_Forms]]
Each [[HTML5]] form UI element must be complete to the following criteria:
1. It must include pleasant and working UI, where appropriate.
See [[HTML5/input]] for more <input> element tests.
* Need more sample/test/wiki pages for other HTML5 UI elements.
2. You must be able to use CSS to style the element, especially the UI that we generate. This includes any pre-defined pseudo-selectors (invalid, required, icon, etc.)
*** ::repeat-item
*** ::repeat-index
** consider additional pseudo-elements based on vendor prefixed pseudos
*** Safari 5 supports pseudo-elements for restyling overflow scrollbars
**** ::webkit-scrollbar-thumb
**** ::webkit-scrollbar-track
**** ::webkit-scrollbar
* 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]
