+1 As an added benefit this will make the documentation task a lot simpler. I fully support using aria and html properties, states and attributes where they apply.
On 31-Jul-08, at 2:41 PM, Jacob Farber wrote: > > What about a more semantic and recycleable approach, where you divide > class names into roles (Selector, State, Presentation)? ------------------------------------------------------ Michelle D'Souza Software Developer, Fluid Project Adaptive Technology Resource Centre University of Toronto _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
