IE9.js
in [JavaScript]
|
From: "Michael Haufe ("TNO")" on 2 Apr 2010 19:15 On Apr 2, 2:38 pm, Scott Sauyet <scott.sau...(a)gmail.com> wrote: > So, I'm curious, how do you apply this to the "id" element. Do you > use it only for CSS, only for Javascript, or do you use it for both? > If the latter, how do you justify the discrepancy? The spec has a similar line for the id attribute. So the same issue applies.
From: "Michael Haufe ("TNO")" on 2 Apr 2010 19:17 On Apr 2, 3:55 pm, Antony Scriven <adscri...(a)gmail.com> wrote: > In other words, use the class attribute purely for semantics. > Sounds more reasonable to me. --Antony No one promoted this.
From: Chris F.A. Johnson on 2 Apr 2010 19:33 On 2010-04-02, David Mark wrote: > Scott Sauyet wrote: >> Michael Haufe ("TNO") wrote: >>> On Apr 2, 12:22 pm, Scott Sauyet <scott.sau...(a)gmail.com> wrote: >>> >>>> Whether or not the specs are relevant, there is still no argument >>>> presented for the point in question: Why should we not use the >>>> "class" attribute for non-CSS purposes? >>> Because meaning and meaningful are two different things. >>> >>> <div class="toolbox">...</div> >>> >>> Does "toolbox" tell me what it looks like, or tell me what it is? >> >> At the risk of actually answering a rhetorical question, I'll bite. >> It should tell you that this DIV element is of the class "toolbox". > > Which tells you nothing at all. Only if you don't know what a tollbox is. -- Chris F.A. Johnson <http://cfajohnson.com> =================================================================== Author: Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress) Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress)
From: David Mark on 2 Apr 2010 20:09 Chris F.A. Johnson wrote: > On 2010-04-02, David Mark wrote: >> Scott Sauyet wrote: >>> Michael Haufe ("TNO") wrote: >>>> On Apr 2, 12:22 pm, Scott Sauyet <scott.sau...(a)gmail.com> wrote: >>>> >>>>> Whether or not the specs are relevant, there is still no argument >>>>> presented for the point in question: Why should we not use the >>>>> "class" attribute for non-CSS purposes? >>>> Because meaning and meaningful are two different things. >>>> >>>> <div class="toolbox">...</div> >>>> >>>> Does "toolbox" tell me what it looks like, or tell me what it is? >>> At the risk of actually answering a rhetorical question, I'll bite. >>> It should tell you that this DIV element is of the class "toolbox". >> Which tells you nothing at all. > > Only if you don't know what a tollbox is. > Even a "toolbox" could mean anything in the context of a class attribute. The mind reels at the possibilities.
From: Thomas 'PointedEars' Lahn on 2 Apr 2010 22:30
Scott Sauyet wrote: > Now, if such toolbox elements should have a certain style applied to > it, include some ".toolbox" rules in your CSS. If there are certain > start-up animations to apply to toolbox elements, use some DOM > searching technique to apply them to all "toolbox" elements. If you > have a toolbox microformat extraction tool, run it against this > element. Yes, that is what a script-kiddie would do. Dump a 64K+ blob of a not understood script from someone else who also has not understood scripting that uses a "DOM searching technique" to find the one relevant element on which to apply a "start-up animation" for a "cool effect". PointedEars -- realism: HTML 4.01 Strict evangelism: XHTML 1.0 Strict madness: XHTML 1.1 as application/xhtml+xml -- Bjoern Hoehrmann |