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 02:27:20 +0000
To: public-script-coord@w3.org
Message-ID: <bug-27354-3890-sUmG7al8x6@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27354

--- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> ---
> Would this allow Anne to replace text like this (from DOM4):

Possibly.

> This effectively is already treating the accessor properties as if they were
> data properties...?

It actually causes a lot of confusion, because it uses the same term
"isTrusted" to refer to both the JS property and the internal state, and while
the former is readonly the latter is not...  So when you talk about setting it,
people aren't sure what you mean until they realize the same term is being used
for two totally different things.

This is why it would be good to make a clear distinction between the externally
visible props and the internal state, so you can unambiguously refer to one or
the other.

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

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