+1 The same can be said for <field> attributes:
<field> <data> - service-name, etc <styling> - title-area-style, etc <interaction> - tooltip, header-link, etc </field> Although this would clutter the field element. On Fri, 2007-02-23 at 16:05 -0800, Chris Howe wrote: > For me the one thing that is holding me back the most from using form > widgets more pervasively is that there are 40+ attributes for the form > element. > > Request for comment: > > 1. Would the form widget be better off with moving the styling > attributes into a subelement as opposed to being attributes of the > <form> tag ie: > > <form> > <styling/> > <actions/> > <field/> > </form> > > 2. If 1, then would it make sense to make a subelement to styling to > account for different media (html vs pdf) or has the pdf styling > already been accomplished well? >
