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 11752 - With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item"
Summary: With the itemscope - it seems unnecessary since it becomes redundant whenever...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
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-01-14 04:37 UTC by contributor
Modified: 2011-08-04 05:05 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-01-14 04:37:49 UTC 
Specification: http://dev.w3.org/html5/md/
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top

Comment:
With the itemscope - it seems unnecessary since it becomes redundant whenever
there's an itemtype - so why not have itemtype="item"

Posted from: 173.61.149.96
Comment 1 Tab Atkins Jr. 2011-01-14 17:49:24 UTC 
The HTML spec editor did user-testing of the feature earlier, and if I recall correctly, several of the test subjects found it much easier if there was an explicit indicator of the container, rather than it being implicit due to the type.
Comment 2 Ian 'Hixie' Hickson 2011-02-15 00:33:46 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
Change Description: no spec change
Rationale: Yeah, what Tab says. I actually agree with the original commenter, and indeed the spec originally just had item="..." and you didn't need to give a value and all was well, but authors in the study uniformly found it confusing and found it much simpler when we simply had them use the two attributes separately instead.
Comment 3 Michael[tm] Smith 2011-08-04 05:05:25 UTC 
mass-move component to LC1