Re: [whatwg] Problems with DOMTokenString

On Thu, 1 Mar 2007, Maciej Stachowiak wrote: > > > > > > If you add DOMString index(unsigned i) and unsigned length, you > > > would also have the ability to enumerate the classes easily, which > > > the API as currently specced lacks. > > > > Do you think we should add this? > > I think it wo

Re: [whatwg] Problems with DOMTokenString

On Feb 11, 2007, at 11:41 PM, Ian Hickson wrote: On Fri, 2 Feb 2007, Maciej Stachowiak wrote: I looked into DOMTokenString with keen interest, because I believe an API for manipulating individual classes of an HTML element is increasingly important as we see more dynamic sites that use CSS st

Re: [whatwg] Problems with DOMTokenString

On Fri, 2 Feb 2007, Maciej Stachowiak wrote: > > I looked into DOMTokenString with keen interest, because I believe an > API for manipulating individual classes of an HTML element is > increasingly important as we see more dynamic sites that use CSS > styling. However, I think the design for th

Re: [whatwg] Problems with DOMTokenString

On Fri, 02 Feb 2007 19:32:05 +0100, Martin Atkins <[EMAIL PROTECTED]> wrote: readonly DOMTokenList mediaList; FYI: "media" takes a _comma_-separated list of media queries. -- Anne van Kesteren

Re: [whatwg] Problems with DOMTokenString

Maciej Stachowiak wrote: Alternative #2: leave the className an ordinary string, but add a new readonly DOMClassList classList property with something like the following interface: interface DOMClassList { void add(DOMString newClass); void remove(DOMString removeClass); bool has

[whatwg] Problems with DOMTokenString

I looked into DOMTokenString with keen interest, because I believe an API for manipulating individual classes of an HTML element is increasingly important as we see more dynamic sites that use CSS styling. However, I think the design for this is not suitable as-is. Summary of DOMTokenStri