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 8763 - Mention that link and meta with itemprop attribute are also flow content
Summary: Mention that link and meta with itemprop attribute are also flow content
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Microdata (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
URL: http://dev.w3.org/html5/md/#content-m...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-15 11:24 UTC by contributor
Modified: 2010-10-05 13:03 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-15 11:24:50 UTC 
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
Comment 1 Lachlan Hunt 2010-01-15 11:33:40 UTC 
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.
Comment 2 Lachlan Hunt 2010-01-15 12:05:40 UTC 
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."
Comment 3 Ian 'Hixie' Hickson 2010-01-17 08:00:44 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.
Comment 4 contributor 2010-01-17 08:01:11 UTC 
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