- From: Cameron McCormack <cam@mcc.id.au>
- Date: Mon, 29 Aug 2011 10:59:03 +1200
- To: Simon Pieters <simonp@opera.com>
- CC: Ian Hickson <ian@hixie.ch>, Jonas Sicking <jonas@sicking.cc>, public-script-coord@w3.org
On 12/08/11 2:03 AM, Simon Pieters wrote: > I tend to agree with Jonas. There's no point in hiding the interface > name from scripts, it's just a source of potential bugs and confusion. I agree here too. I don't see any particular advantage from avoiding using inheritance here without any messing around of prototypes. If the prose in the spec is awkward because you would need to say "the DedicatedWorkerGlobalScope or SharedWorkerGlobalScope object" rather than just "the WorkerGlobalScope object", then I wouldn't worry and either introduce a term "worker global scope object" to mean that, or to reference it as "the WorkerGlobalScope object" given that the two more derived interfaces are actually WorkerGlobalScopes. In http://www.w3.org/Bugs/Public/show_bug.cgi?id=10337 I had introduced [CopyInheritedPrototype] to satisfy this use case (and to avoid [Supplemental]) but I am beginning to think there's not a strong enough reason to have it.
Received on Sunday, 28 August 2011 22:59:48 UTC