For an example :
test(function () {
assert_equals( makeEl('div',{itemtype:' '}).itemType[0],
window.undefined );
}, 'itemType[index] must be undefined for out-of-range index');
makeEl method creates an element <div> with empty itemtype(0 tokens). Test
expects itemTpye[0] should return undefined, in our case it returns null.
According to the spec itemtpye attribute is a space-separated list.
http://www.whatwg.org/specs/web-apps/current-work/#attr-itemtype
We have defined itemtype attribute as :
readonly attribute [Conditional=MICRODATA] DOMSettableTokenList itemType;
DOMSettableTokenList returns null for out-of-range index.
So I thought it is specific to DOMSettableTokenList implementation. Or is
this the bug in our DOMSettableTokenList implementation? There are many
tests failing because of this.
Do you think, we should first resolve all these test issues and then think
of enabling feature by default? In that case I will raise a new bug and we
can then discuss the failed tests there.
Regards,
Arko
On Tue, Jul 31, 2012 at 12:51 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> On Mon, Jul 30, 2012 at 11:51 PM, Arko Saha <ngh...@motorola.com> wrote:
>
>> I have tested the test :
>> http://w3c-test.org/html/tests/submission/Opera/microdata/001.html
>> 255 Pass
>> 82 Fail
>>
>> Most of the failed cases are specific to their implementation and for
>> others, I need to check.
>>
>
> What do you mean by "specific to their implementation"? I would expect any
> test submitted to the W3C test suite to be cross browser. Tests shouldn't
> include vendor prefixes for example.
>
> - Ryosuke
>
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
