IE9.js
in [JavaScript]
|
From: "Michael Haufe ("TNO")" on 2 Apr 2010 22:50 On Apr 2, 6:12 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > That is not a mistake at all. If going to make the conclusions you did, > then you're going to have to provide reasons. These reasons have been enumerated across a number of posts already. The biggest issue is that classes can have a predefined meaning to some implementations. What makes it worse is that some of these predefined classes behave differently depending on the element its used upon. So <p class="email"/> means nothing by itself, but <p class="copyright"/> has a predefined meaning as can be seen in HTML5.
From: Garrett Smith on 2 Apr 2010 23:19 Michael Haufe ("TNO") wrote: > On Apr 2, 6:12 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > >> That is not a mistake at all. If going to make the conclusions you did, >> then you're going to have to provide reasons. > > These reasons have been enumerated across a number of posts already. > The biggest issue is that classes can have a predefined meaning to > some implementations. What makes it worse is that some of these > predefined classes behave differently depending on the element its > used upon. So <p class="email"/> means nothing by itself, but <p > class="copyright"/> has a predefined meaning as can be seen in HTML5. The biggest reason is html5 predefined clasees? What behavior can I look for, and in which implementations can that be seen? I read that predefined classes went away in 2007[1]. It looks to have been replaced by "microdata". I haven't looked to deeply into microdata. [1]<http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-August/012299.html> -- Garrett comp.lang.javascript FAQ: http://jibbering.com/faq/
From: "Michael Haufe ("TNO")" on 3 Apr 2010 00:42 On Apr 2, 10:19 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > The biggest reason is html5 predefined clasees? What behavior can I look > for, and in which implementations can that be seen? > > I read that predefined classes went away in 2007[1]. I truly hope that is the case.
From: "Michael Haufe ("TNO")" on 3 Apr 2010 01:07 On Apr 2, 11:42 pm, "Michael Haufe (\"TNO\")" <t...(a)thenewobjective.com> wrote: > On Apr 2, 10:19 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > > > The biggest reason is html5 predefined clasees? What behavior can I look > > for, and in which implementations can that be seen? > > > I read that predefined classes went away in 2007[1]. > > I truly hope that is the case. Note that this doesn't refute the underlying problem, but it does prevent one issue that has bugged me for some time. Also, this doesn't discount future uses of the class/id attributes in this manner since the spec allows it. On Apr 2, 10:19 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > It looks to have been replaced by "microdata". I haven't looked to > deeply into microdata. Microdata does provide somewhat of a solution to the semantic/ presentaion problems I've described thus far, but Thomas has voiced his issues with that already and I must agree.
From: Garrett Smith on 3 Apr 2010 02:09
Michael Haufe ("TNO") wrote: > On Apr 2, 11:42 pm, "Michael Haufe (\"TNO\")" > <t...(a)thenewobjective.com> wrote: >> On Apr 2, 10:19 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: >> >>> The biggest reason is html5 predefined clasees? What behavior can I look >>> for, and in which implementations can that be seen? >>> I read that predefined classes went away in 2007[1]. >> I truly hope that is the case. > > Note that this doesn't refute the underlying problem, Underlying problem? Earlier you wrote that the biggest issue was predefined classes. Do you want say something more about how using class forces one to understand its context in the markup? Did the `email` example not provide a sufficient counterexample? What else is there? -- Garrett comp.lang.javascript FAQ: http://jibbering.com/faq/ |