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

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Boris Zbarsky from comment #2)
> I think the idea is to annotate the places where a spec is defined in terms
> of internal slots.   The spec for innerHTML wouldn't be.
> 
> In general, nothing requires an implementation to have any internal slots,
> of course; just to act as if it does if that's how a spec is defined.

Would this allow Anne to replace text like this (from DOM4):

  The stopPropagation() method must set the stop propagation flag. 

With a reference to the Event's [[stopPropagation]] slot value?

In the same spec, he uses other prose to initialize various accessors:

  To initialize an event, with type, bubbles, and cancelable, run these steps: 
  1.Set the initialized flag. 
  2.If the dispatch flag is set, terminate these steps. 
  3.Unset the stop propagation flag, stop immediate propagation flag, and
canceled flag. 
  4.Set the isTrusted attribute to false. 
  5.Set the target attribute to null. 
  6.Set the type attribute to type. 
  7.Set the bubbles attribute to bubbles. 
  8.Set the cancelable attribute to cancelable. 

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

Is the distinction really that necessary?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 18 November 2014 01:19:51 UTC

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