This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11305 - Remove stuff present in DOM Core
Summary: Remove stuff present in DOM Core
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dvcs.w3.org/hg/domcore/raw-fil...
Whiteboard:
Keywords:
Depends on: 13387
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-11 21:35 UTC by Ms2ger
Modified: 2011-08-04 05:05 UTC (History)
7 users (show)

See Also:


Attachments

Description Ms2ger 2010-11-11 21:35:30 UTC
In particular you could drop

2.1.3 DOM trees
* root element
* in a Document.
* home subtree
* tree order
* text node, as there are no CDATASections anymore

2.3 Case-sensitivity and string comparison
* case-sensitive
* ASCII case-insensitive
* Converting a string to uppercase
* Converting a string to lowercase

2.5.1 Common parser idioms
* space characters
* collect a sequence of characters
* skip whitespace

2.5.7 Space-separated tokens
Entirely

2.6.2 Dynamic changes to base URLs
Update to use DOM Core terminology (<http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#element>).

2.8.2 Collections
* collections
* represents

2.8.2.1 HTMLCollection
Entirely

2.8.3 DOMTokenList
2.8.4 DOMSettableTokenList
Entirely

3.1 Documents
* XML documents
* HTML documents

3.1.3 Resource metadata management
* compatMode and related definitions

3.1.4 DOM tree accessors
* getElementsByClassName

3.1.5 Creating documents
Entirely

3.2.3.1 The id attribute
* concept-id

3.3 APIs in HTML documents
Entirely
Comment 1 Ian 'Hixie' Hickson 2010-12-29 09:01:54 UTC
How mature is Web DOM Core? My impression was that Anne was overloaded with different specs and that it wasn't being actively updated (case in point, it hasn't changed in over 2 months).
Comment 2 Ian 'Hixie' Hickson 2011-01-22 00:24:30 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 1
Comment 3 Ian 'Hixie' Hickson 2011-07-26 23:25:08 UTC
(In reply to comment #0)
> In particular you could drop
> 
> 2.1.3 DOM trees
> * root element
> * in a Document.
> * home subtree
> * tree order
> * text node, as there are no CDATASections anymore
> 
> 2.3 Case-sensitivity and string comparison
> * case-sensitive
> * ASCII case-insensitive
> * Converting a string to uppercase
> * Converting a string to lowercase
> 
> 2.5.1 Common parser idioms
> * space characters
> * collect a sequence of characters
> * skip whitespace
> 
> 2.5.7 Space-separated tokens
> Entirely

For these I'd rather share text than reference DOM Core, since not everything I need is in DOM Core and it doesn't seem useful to move the rest of the stuff to DOM Core since DOM Core doesn't use it.

Sharing text would consist of slurping up the DOM Core text and snipping it out and then merging that text into the HTML spec. I'm happy to do that; file another bug when ready.


> 2.6.2 Dynamic changes to base URLs
> Update to use DOM Core terminology
> (<http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#element>).

Can you elaborate on this in a new bug?


> 2.8.2 Collections
> * collections
> * represents
> 2.8.2.1 HTMLCollection
> Entirely

Done.

However, note that HTMLCollection in DOM Core doesn't define the 'caller' which is needed for compat according to certain UAs.

[remainder yet to be examined]
Comment 4 Ian 'Hixie' Hickson 2011-07-26 23:56:39 UTC
(continuing...)
> 2.8.3 DOMTokenList
> 2.8.4 DOMSettableTokenList
> Entirely

Done.


> 3.1 Documents
> * XML documents
> * HTML documents

Done.


> 3.1.3 Resource metadata management
> * compatMode and related definitions

Done. Also the charset stuff.


[remainder yet to be examined]
Comment 5 Ian 'Hixie' Hickson 2011-07-27 23:06:14 UTC
(continuing...)
> 
> 3.1.4 DOM tree accessors
> * getElementsByClassName

Done. Did you get the memo about getAncestorByClassName()?


> 3.1.5 Creating documents
> Entirely

Done.


> 3.2.3.1 The id attribute
> * concept-id

I've left this. It's just exposition.


> 3.3 APIs in HTML documents
> Entirely

See bug 11717 and bug 11719.


EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: removed sections listed above
Rationale: See comments above.
Comment 6 Ms2ger 2011-07-28 08:39:09 UTC
(In reply to comment #5)
> (continuing...)
> > 
> > 3.1.4 DOM tree accessors
> > * getElementsByClassName
> 
> Done. Did you get the memo about getAncestorByClassName()?

Yes.
Comment 7 Michael[tm] Smith 2011-08-04 05:05:03 UTC
mass-moved component to LC1