[Webkit-unassigned] [Bug 65737] Remove LegacyDefaultOptionalArguments flag from canvas IDL files

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=65737





--- Comment #3 from Mark Pilgrim <pilgrim at chromium.org>  2011-08-04 19:12:11 PST ---
(In reply to comment #2)
> (From update of attachment 103021 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=103021&action=review
> 
> > Source/WebCore/html/canvas/OESVertexArrayObject.idl:38
> > -        [StrictTypeChecking] void         deleteVertexArrayOES(in WebGLVertexArrayObjectOES arrayObject);
> > -        [StrictTypeChecking] boolean      isVertexArrayOES(in WebGLVertexArrayObjectOES arrayObject);
> > -        [StrictTypeChecking] void         bindVertexArrayOES(in WebGLVertexArrayObjectOES arrayObject) raises(DOMException);
> > +        [StrictTypeChecking] void         deleteVertexArrayOES(in [Optional=CallWithDefaultValue] WebGLVertexArrayObjectOES arrayObject);
> > +        [StrictTypeChecking] boolean      isVertexArrayOES(in [Optional=CallWithDefaultValue] WebGLVertexArrayObjectOES arrayObject);
> > +        [StrictTypeChecking] void         bindVertexArrayOES(in [Optional=CallWithDefaultValue] WebGLVertexArrayObjectOES arrayObject) raises(DOMException);
> 
> Is there any bad interaction between StrictTypeChecking and CallWithDefaultValue?

No. StrictTypeChecking adds some additional type checking after the function declaration is constructed. See line 936 of Source/WebCore/bindings/scripts/CodeGeneratorV8.pm for details. It does not interact with [Optional=CallWithDefaultValue].

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.