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 18950 - consider to make <meta> accepting <meta> children
Summary: consider to make <meta> accepting <meta> children
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-21 13:43 UTC by Giorgio
Modified: 2013-04-05 14:11 UTC (History)
4 users (show)

See Also:

Attachments

Description Giorgio 2012-09-21 13:43:30 UTC 
hi,

consider this snippet:

<div itemprop="primaryImageOfPage" itemscope itemtype="http://schema.org/ImageObject">
	<meta itemprop="representativeOfPage" content="true">
	<meta itemprop="contentUrl" content="/...gif">
	<div itemprop="thumbnail" itemscope itemtype="http://schema.org/ImageObject">
		<meta itemprop="contentUrl" content="/...gif">
	</div>
</div>

now, this in <head> tag is not allowed, but nesting is required by microdata in this case, so what about:

<meta itemprop="primaryImageOfPage" itemscope itemtype="http://schema.org/ImageObject">
	<meta itemprop="representativeOfPage" content="true">
	<meta itemprop="contentUrl" content="/...gif">
	<meta itemprop="thumbnail" itemscope itemtype="http://schema.org/ImageObject">
		<meta itemprop="contentUrl" content="/...gif">
	</meta>
</meta>
Comment 1 Robin Berjon 2013-04-05 14:11:02 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: Rejected
Rationale: Irrespective of the value of the use case, I don't believe that there's a way in which we could change the parsing algorithm to make it possible for a void element to suddenly start accepting children, at least not without introducing really complex heuristics.