8763 2010-01-15 11:24:50 +0000 Mention that link and meta with itemprop attribute are also flow content 2010-10-05 13:03:10 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML Microdata (editor: Ian Hickson) unspecified Other other CLOSED FIXED http://dev.w3.org/html5/md/#content-models P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31074 0 contributor 2010-01-15 11:24:50 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-link-element Comment: Remove redundant category "If the itemprop attribute is present: flow content.", as this is already covered by phrasing content. This applies to both the link and meta elements Posted from: 213.236.208.22 31075 1 lachlan.hunt 2010-01-15 11:33:40 +0000 Also note that the equivalent section in the HTML5 Microdata delta spec only states that these elements are phrasing content. So removing the flow content category will resolve this discrepancy too. 31076 2 lachlan.hunt 2010-01-15 12:05:40 +0000 Changing this bug to be about correcting the discrepancy in the Microdata spec. It seems that all phrasing content elements are explicitly listed as being in Flow Content, so this isn't really a bug in the complete spec as I thought. This statement from the Micordata delta spec should be updated to mention Flow Content too. "If the itemprop attribute is present on link or meta, they are phrasing content. The link and meta elements may be used where phrasing content is expected if the itemprop attribute is present." 31091 3 ian 2010-01-17 08:00:44 +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. 31092 4 contributor 2010-01-17 08:01:11 +0000 Checked in as WHATWG revision r4598. Check-in comment: make the way categories are listed more consistent with the HTML5 spec. http://html5.org/tools/web-apps-tracker?from=4597&to=4598