Re: [whatwg] Microdata getItems()
On 09/08/11 20:48, Ian Hickson wrote: On Tue, 9 Aug 2011, Rob Crowther wrote: Correct. Browsers aren't expected to know about the vocabularies, let alone validate them. Thanks. I think this could be made more clear in the spec. However if I remove itemscope from the element the Opera beta implementation still returns it as a top level microdata item even though it is now invalid. Is this expected behaviour? No. Looks like this was me doing something stupid, Opera is indeed only returning the items with both itemscope and itemtype. Rob
Re: [whatwg] Microdata getItems()
On Tue, 9 Aug 2011, Rob Crowther wrote: > > I just want to confirm that my understanding of this is correct: > getItems() will return a NodeList of top level microdata items and this > is irrespective of whether or not the items are actually valid in terms > of their type? That is, it is the developer's responsibility to confirm > that the vCard has an fn and an n before further processing? Correct. Browsers aren't expected to know about the vocabularies, let alone validate them. > One further question - if an itemtype attribute is present there must > also be an itemscope. However if I remove itemscope from the element > the Opera beta implementation still returns it as a top level microdata > item even though it is now invalid. Is this expected behaviour? No. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
[whatwg] Microdata getItems()
I just want to confirm that my understanding of this is correct: getItems() will return a NodeList of top level microdata items and this is irrespective of whether or not the items are actually valid in terms of their type? That is, it is the developer's responsibility to confirm that the vCard has an fn and an n before further processing? It makes sense to me because I don't expect the browser to be downloading random vocabularies off the internet to check these things, but it doesn't seem to be explicitly referenced in the spec. There is a section which talks about de-referencing says that the browser can dereference the URL to provide item specific processing, but only if the applicable specification allows it. One further question - if an itemtype attribute is present there must also be an itemscope. However if I remove itemscope from the element the Opera beta implementation still returns it as a top level microdata item even though it is now invalid. Is this expected behaviour? Rob