On Dec 27, 1:56 pm, buda <[email protected]> wrote: > > 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. > > If document is decleared as strict or transitional - it must be valid > - otherwise it switch to quirck mode - am I right > Custom attributes are not valid in thiese modes only in quirck mode
If document is declared as strict or transitional it must validate against corresponding DTD's in order to be valid. When there's no declaration, there's nothing to validate against. If quirks mode is triggered by lack of doctype declaration, then validity does not even apply, since there's no declaration to validate against. Am I missing something? > > It is indeed useful. HTML5 even introduced custom data-* attributes > > [1] > > When will it the standard? 2022 > > > 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. > > Element#store, Element#retrieve - where can I view it? http://github.com/sstephenson/prototype/tree/master/src/dom/dom.js#L1221 [...] -- 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 -~----------~----~----~----~------~----~------~--~---
