[webkit-dev] Enable MICRODATA feature by default

Arko Saha nghq36 at motorola.com
Tue Jul 31 00:55:26 PDT 2012

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.
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.


On Tue, Jul 31, 2012 at 12:51 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:

> On Mon, Jul 30, 2012 at 11:51 PM, Arko Saha <nghq36 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120731/20597b21/attachment.html>

More information about the webkit-dev mailing list