This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html Multipage: http://www.whatwg.org/C#dedicated-workers-and-the-dedicatedworkerglobalscope-interface Complete: http://www.whatwg.org/c#dedicated-workers-and-the-dedicatedworkerglobalscope-interface Comment: Now that the "relevant namespace object" term has gone from Web IDL (since modules have been removed) some text around here needs to be rewritten. You probably want to refer to you don't need to mention the ECMAScript global object specifically, but instead you might want to refer to Web IDL's #dfn-expose, which can be used to control which interfaces are exposed in a particular ECMAScript global environment. Just say "ECMAScript global environments for dedicated workers must not _expose_ the SharedWorkerGlobalScope interface." and vice versa. I think that should be sufficient. Posted from: 150.101.156.250 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0a1) Gecko/20111209 Firefox/11.0a1
This bug was cloned to create bug 18003 as part of operation convergence.
I've tried to fix this, but I've no idea if what I wrote is right. Please do review it.
Checked in as WHATWG revision r7226. Check-in comment: Upgrade Web IDL terminology. http://html5.org/tools/web-apps-tracker?from=7225&to=7226
The change looks good to me. (The transitive requirement is probably a bit of a pain if you want to know, from looking at the spec, whether a given interface should be exposed or not.)
*** Bug 17166 has been marked as a duplicate of this bug. ***
*** Bug 18188 has been marked as a duplicate of this bug. ***