Several people gave feedback regarding DOMTokenList. In particular about
making add()/remove() accept multiple values. Your feedback is now tracked
over here as DOMTokenList moved from HTML to DOM:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13999
Having said that, we will likely
On Thu, Jul 30, 2009 at 6:38 PM, Ian Hicksoni...@hixie.ch wrote:
On Mon, 27 Jul 2009, Jonas Sicking wrote:
In general, I try to be as conservative as possible in making changes
to the DOM. Are the algorithms really as complicated as you're making
out? They seem pretty trivial to me.
At
On Mon, 20 Jul 2009, Sylvain Pasche wrote:
1) What's the reason for preserving whitespace when a DOMTokenList
method is changing the attribute?
As a general rule, I try to make the APIs as minimally invasive as
possible. Whenever we have failed to do this, we end up confusing authors
--
On Mon, 6 Jul 2009, Sylvain Pasche wrote:
I'm looking at the Gecko implementation of element.classList. I had a
few comments about the spec.
1) http://html5.org/tools/web-apps-tracker?from=3253to=3254 missed something.
There is still a mention of alphabetical sort order in the beginning
Regarding DOMTokenList, why not:
contains(): true
add,remove,toggle(): no effect?
Are there situations that would require an exception to be thrown, or else
the page would go out in a blast?
Chris
On 7/6/2009 9:08 AM, Kristof Zelechovski wrote:
Regarding DOMTokenList, why not:
contains(): true
add,remove,toggle(): no effect?
That could be an option. There is already a INVALID_CHARACTER_ERR
exception thrown if the token contains spaces. So I think it would be
consistent
Hi,
I'm looking at the Gecko implementation of element.classList. I had a
few comments about the spec.
1) http://html5.org/tools/web-apps-tracker?from=3253to=3254 missed
something. There is still a mention of alphabetical sort order in the
beginning of section 2.8.3:
element = tokenlist .
