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

[Bug 18362] Make stringifiers not take into account expandos

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Dec 2012 04:43:35 +0000
To: public-script-coord@w3.org
Message-ID: <bug-18362-3890-hJZcYCExTX@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18362

Cameron McCormack <cam@mcc.id.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Cameron McCormack <cam@mcc.id.au> ---
I don't know, I tend to think that for example

  interface Blah {
    stringifier readonly attribute DOMString something;
  };

means

  Object.defineProperty(Blah.prototype, "something",
                        { get: function() { return <internal state>; }, ...);
  Blah.prototype.toString = function() { return this.something; }

rather than

  Object.defineProperty(Blah.prototype, "something",
                        { get: function() { return <internal state>; }, ...);
  Blah.prototype.toString = function() { return <internal state>; }

and I feel like it is a more natural way of implementing it.  It's in line with
what we're doing for [PutForwards], too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 December 2012 04:43:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:08 UTC