Bug 47812 – V8 binding for DOMSettableTokenList

• Status: RESOLVED
• Resolution: FIXED
• Component: DOM

[Kenichi Ishibashi]

Implement V8 binding for DOMSettableTokenList. This issue is a part of implementing the <output> element. See https://bugs.webkit.org/show_bug.cgi?id=29363 for more details.

[Kenichi Ishibashi]

Created attachment 72479 [details]
Patch V0

[WebKit Commit Bot]

Comment on attachment 72479 [details]
Patch V0

Clearing flags on attachment: 72479

Committed r71007: <http://trac.webkit.org/changeset/71007>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Erik Arvidsson]

Comment on attachment 72479 [details]
Patch V0

View in context: https://bugs.webkit.org/attachment.cgi?id=72479&action=review

Also, why do we need custom indexedPropertyGetter? It wasn't needed for classList. The codegen knows how to generate this.

> WebCore/bindings/v8/custom/V8DOMSettableTokenListCustom.cpp:39
> +    return v8String(list->item(index));

This does not look right since we should return null when index is out of bounds. ([ConvertNullStringTo=Null]  in the idl)

[Kenichi Ishibashi]

Hi Erik,

Thank you for your comment.

(In reply to comment #4)
> Also, why do we need custom indexedPropertyGetter? It wasn't needed for classList. The codegen knows how to generate this.

It looks like that the codegen for V8 bindings does not consider the inheritance of the interface and doesn't generate indexedPropertyGetter automatically. On the other hand, the codegen for JSC consider the inheritance of the interface and generate getter function automatically. To manage these two case, we need to custom function.

> > WebCore/bindings/v8/custom/V8DOMSettableTokenListCustom.cpp:39
> > +    return v8String(list->item(index));
> 
> This does not look right since we should return null when index is out of bounds. ([ConvertNullStringTo=Null]  in the idl)

Yes, I've made a mistake and I'll fix it in the patch for https://bugs.webkit.org/show_bug.cgi?id=29363. Thank you for correcting.