PROTECTED]
To: Jonas Sicking [EMAIL PROTECTED]
Cc: Webapps public-webapps@w3.org, Web APIs WG [EMAIL PROTECTED],
Daniel Glazman [EMAIL PROTECTED]
Sent: Monday, June 23, 2008 7:23:47 PM GMT -05:00 US/Canada Eastern
Subject: Element Nodelist - ISSUE-6 (was: ElementTraversal progress?)
Hi, Jonas, Daniel
WG [EMAIL PROTECTED], Daniel
Glazman [EMAIL PROTECTED]
Sent: Monday, June 23, 2008 7:23:47 PM GMT -05:00 US/Canada Eastern
Subject: Element Nodelist - ISSUE-6 (was: ElementTraversal progress?)
Hi, Jonas, Daniel-
Jonas Sicking wrote (on 6/23/08 2:03 PM):
What about the issue I raised here
Hi, Jonas, Daniel-
Jonas Sicking wrote (on 6/23/08 2:03 PM):
What about the issue I raised here:
http://lists.w3.org/Archives/Public/public-webapps/2008AprJun/0214.html
Which no one replied to.
If you implement the HTML DOM you should already have code that not only
filters out elements,
Sounds good to me.
/ Jonas
Doug Schepers wrote:
Hi, Jonas, Daniel-
Jonas Sicking wrote (on 6/23/08 2:03 PM):
What about the issue I raised here:
http://lists.w3.org/Archives/Public/public-webapps/2008AprJun/0214.html
Which no one replied to.
If you implement the HTML DOM you should
Doug Schepers wrote:
I will create an Element Nodelist specification right away, and if it is
approved to go forward (and I don't see why it wouldn't be, since there
is considerable support), I am confident that this would not slow down
deployment in desktop browsers, and so authors should
