12911 2011-06-08 14:48:54 +0000 Incorrect order of "a" properties in itemref example 2011-08-04 05:05:25 +0000 1 1 1 Unclassified HTML WG LC1 HTML Microdata (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#names:-the-itemprop-attribute P3 blocker --- 1 contributor ian ian mike philipj public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 49320 0 contributor 2011-06-08 14:48:54 +0000 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 49321 1 philipj 2011-06-08 14:52:05 +0000 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. 50818 2 ian 2011-07-07 23:10:56 +0000 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. 50819 3 contributor 2011-07-07 23:12:09 +0000 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 52928 4 mike 2011-08-04 05:05:25 +0000 mass-move component to LC1