W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

[Bug 27354] Internal slots

From: <bugzilla@jessica.w3.org>
Date: Tue, 18 Nov 2014 10:10:57 +0000
To: public-script-coord@w3.org
Message-ID: <bug-27354-3890-16JlSxUE8t@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27354

--- Comment #5 from Anne <annevk@annevk.nl> ---
(In reply to Travis Leithead [MSFT] from comment #3)
> Is the distinction really that necessary?

Note that while having internal slots would make many specifications far less
ambiguous about what is actually going on, the real driver here is bug 27355.
When you instantiate an object, you need to figure out if it has associated
objects that need to be instantiated as well (and make sure they all have the
correct Realm). Having a concept of internal slots helps formalizing finding
those associated objects.

interface Document {
  readonly attribute DOMImplementation implementation;
}

Helps establishing that when a Document is created, a DOMImplementation object
is created as well and stored in Document's [[implementation]].

(A nice follow up might be to have default IDL getter/setter implementations
for these scenarios. E.g. for the above the getter will simply return
this@[[implementation]]. There's no need to spell that out in the specification
anymore.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 18 November 2014 10:11:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC