On Dec 27, 6:15 am, buda <[email protected]> wrote: > From one hand - custom attributes, if they are not described in DTD, > are evil for valid Transitional or Strict modes - they lead document > to quirck mode
No. Quirks mode is triggered by the lack of doctype declaration, not the presence of custom attributes. IE is the only exception in that it *also* triggers quirks when anything non-whitespace precedes doctype declaration. > > From another hand - they make the life easy for developers with their > ability to store a lot of metadata like: required="true" mask="^w+..." > oldValue="345" emptyVlue="0" min="10" max="1000" rowID="1213" and etc It is indeed useful. HTML5 even introduced custom data-* attributes [1] > > there is an offer to store whole metadata into css classname attribute > (it maybe a very long string with keypairs) - which as for me its very > very complex to analyze and modify > > What do you think about it? I think you should use class attributes or some alternative approach, and keep your markup valid. On a side note, there's a data manipulation addition in prototype's trunk; Element#store and Element#retrieve. You might want to look into that. [1] http://www.whatwg.org/specs/web-apps/current-work/#custom-data-attribute -- kangax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
