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 12911 - Incorrect order of "a" properties in itemref example
Summary: Incorrect order of "a" properties in itemref example
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 blocker
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 14:48 UTC by contributor
Modified: 2011-08-04 05:05 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2011-06-08 14:48:54 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#names:-the-itemprop-attribute

Comment:
Incorrect order of "a" properties in itemref example

Posted from: 83.218.67.122
User agent: Opera/9.80 (X11; Linux x86_64; U; Opera Next; en) Presto/2.8.131 Version/11.50
Comment 1 Philip Jägenstedt 2011-06-08 14:52:05 UTC
The spec says:

In the following example, the "a" property has the values "1" and "2", in that order, but whether the "a" property comes before the "b" property or not is not important:

<div itemscope itemref="x">
 <p itemprop="b">test</p>
 <p itemprop="a">2</p>
</div>
<div id="x">
 <p itemprop="a">1</p>
</div>

I say:

This seems to be wrong. <http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#crawl-the-properties> clearly sorts all properties in tree order, so the order should be "2", "1" in this case.

I've verified with http://foolip.org/microdatajs/live/ that implementing the crawl algorithm (mostly) as specified doesn't do what the example claims.
Comment 2 Ian 'Hixie' Hickson 2011-07-07 23:10:56 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

I used to sort them in the order you'd find them (so the itemref="" attribute's value's order was important) and forgot to update the example when I changed that. Good catch.
Comment 3 contributor 2011-07-07 23:12:09 UTC
Checked in as WHATWG revision r6282.
Check-in comment: Example was out of date.
http://html5.org/tools/web-apps-tracker?from=6281&to=6282
Comment 4 Michael[tm] Smith 2011-08-04 05:05:25 UTC
mass-move component to LC1