Re: [whatwg] Interface objects in Web Workers

2009-12-01 Thread Ian Hickson
On Wed, 25 Nov 2009, Simon Pieters wrote:

 The Interface objects and constructors section says
 
 There must be no interface objects and constructors available in the 
 global scope of scripts whose script's global object is a 
 WorkerGlobalScope object except for the following:
 
 WorkerGlobalScope, WorkerLocation, Navigator, AbstractWorker, ErrorEvent 
 are not in the list. Is this intentional? If they're intended to not 
 create interface objects, it would be clearer if the IDLs had 
 [NoInterfaceObject].

I've changed that section to be more precise legalese that automatically 
does the right thing.


 Should EventTarget and Event be in the list?

These are now automatically covered by the new magical text in the 
aforementioned section. (Basically I said that any interfaces relevant to 
exposed APIs are automatically to be available.)

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


[whatwg] Interface objects in Web Workers

2009-11-25 Thread Simon Pieters

The Interface objects and constructors section says

There must be no interface objects and constructors available in the
global scope of scripts whose script's global object is a
WorkerGlobalScope object except for the following:

WorkerGlobalScope, WorkerLocation, Navigator, AbstractWorker, ErrorEvent
are not in the list. Is this intentional? If they're intended to not
create interface objects, it would be clearer if the IDLs had
[NoInterfaceObject].

Should EventTarget and Event be in the list?

--
Simon Pieters
Opera Software