W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 13610] [DOM Core] Remove HTMLElement.id

From: <bugzilla@jessica.w3.org>
Date: Mon, 26 Sep 2011 19:56:26 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R8HHu-0004Bv-Sr@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13610

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[DOM Core] Remove           |[DOM Core] Remove
                   |HTMLElement.{id,className,c |HTMLElement.id
                   |lassList}                   |

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-26 19:56:25 UTC ---
Let's split the ID and class issues up here, and use this bug just for the ID
side. Once the class complications are resolved, if it still requires changes
to the HTML spec, file a new bug.

As far as ID goes, the DOM Core spec currently has the following issues:

 - it doesn't allow for multiple IDs per element. While I'm sure we all think
that allowing that is problematic, and we're working to make it impossible, the
truth of the matter is that we have so far had at least 4 ways to set IDs
(id="", xml:id="", IDness in DTD, and the old DOM APIs), and I see no reason to
believe that we'll prevent people from making up new ones in the future. So we
should at least admit the possibility.

 - no special handling is defined for when the id="" attribute's value is the
empty string.

Once these are resolved I can remove the relevant sentences from the HTML spec.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 26 September 2011 19:56:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:19 UTC