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 7964 - Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order
Summary: Either change the "properties of an item" algorithm to be tree-order or HTMLP...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-10-18 22:48 UTC by contributor
Modified: 2010-10-04 14:57 UTC (History)
5 users (show)

See Also:


Description contributor 2009-10-18 22:48:21 UTC

Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order

Posted from:
Comment 1 Philip Jägenstedt 2009-10-18 22:52:06 UTC
IRC discussion logged at

Which should be changed depends on which is easier to implement. Unless there's a hurry, perhaps we can wait for the first implementors to give feedback before deciding.
Comment 2 Philip Jägenstedt 2009-10-19 11:36:05 UTC
Of course it's PropertyNodeList.values, not HTMLPropertyCollection.values.
Comment 3 Ian 'Hixie' Hickson 2009-10-21 10:10:34 UTC
Did you ever decide which was easier to implement?
Comment 4 Philip Jägenstedt 2009-10-21 10:43:56 UTC
No, I'm waiting for some kind of conclusion on the discussion started at

As it stands:

Using algorithm-order requires a fair bit of complexity to avoid loops and cannot reuse general collection code which only supports document-order.

Using document-order would require either first doing the above and then sorting, or first doing a more limited traversal to determine which id's should be included and after that walking the entire document.

Both are more complex than any other type of collection, neither is impossible, but my guesstimate is that algorithm-order for everything (including the NodeList returned by .getItems()) would be easier, but as I said I'm waiting for the conclusion of the above discussion to see if there can't be an <itemref>-free solution.

Leaving as NEEDSINFO, myself being the one who needs info.
Comment 5 Ian 'Hixie' Hickson 2009-10-21 12:16:02 UTC
Reopening — I'll change the spec to be consistent, at least, and then we can change it to the other option once we know which is best.
Comment 6 Ian 'Hixie' Hickson 2009-10-22 23:15:29 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:

Status: Rejected
Change Description: no spec change
Rationale: This is irrelevant now that <itemref> is replaced by itemref="", since itemref="" always gets processed in tree order.