[Public WebGL] Should WebGLContextAttributes be a callback interface?

Cameron McCormack [email protected]
Sun Apr 8 19:49:42 PDT 2012


Cameron McCormack:
>> Would a DOM object be able to create and return its own objects that
>> implement callback interfaces?

Boris Zbarsky:
> I'm not sure what you mean.  For one thing, it's not really quite
> defined what it means to "implement a callback interface"...

Any JS non-platform object can serve as a callback interface object.  So 
perhaps with

   callback interface A {
     attribute long x;
     attribute long y;
     void f();
   };

   interface B {
     A g();
   };

calling B.g() could return a new JS native object with "x", "y" and "f" 
properties.

The same question arises with callback functions.  If you defined

   callback SomeCallback = void ();

   interface C {
     attribute SomeCallback handler;
   };

should C.handler be allowed to return a Function object that script 
didn't create?  Maybe.

-----------------------------------------------------------
You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------





More information about the public_webgl mailing list