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 18978 - I have a hard time to understand why we need to specify itemscope when we have an itemtype. like in: <section itemscope itemtype="http://example.org/animals#cat"> I finally find this bug report https://www.w3.org/Bugs/Public/show_bug.cgi?id=11752 but I th
Summary: I have a hard time to understand why we need to specify itemscope when we hav...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-23 11:28 UTC by contributor
Modified: 2013-05-08 17:39 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2012-09-23 11:28:27 UTC 
Specification: http://dev.w3.org/html5/md/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
I have a hard time to understand why we need to specify itemscope when we have
an itemtype. like in:

<section itemscope itemtype="http://example.org/animals#cat">

I finally find this bug report
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11752 but I think the
documentation should be clear about it.


Posted from: 194.230.159.98
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20100101 Firefox/15.0.1
Comment 1 Ian 'Hixie' Hickson 2012-11-25 05:34:47 UTC 
We did usability testing (like, actual testing with one-way glass and everything) and it turns out that this one change (from having a single attribute item="" which could take as its value the type, to separate attributes for scope and type) made all the difference in how easily people understood what was going on.