Ok, I've filed this bug to use @@toStringTag in the debugger instead of Debugger.Object.prototype.class: https://bugzilla.mozilla.org/show_bug.cgi?id=1278310
On Mon, Jun 6, 2016 at 10:35 AM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 6/6/16 12:23 PM, Nick Fitzgerald wrote: > >> Yes (via the `Debugger.Object.prototype.class` getter) but unless I've >> misunderstood the scope of this proposal, the class name exposed by that >> getter should not change, only the `Object.prototype.toString.call(thing)` >> would change. >> > > You misunderstood the scope. We would be changing the class string if we > change the web-facing behavior here. > > Or put another way, if we want to change to @@toStringTag for DOM objects > (which we do) and _if_ we want that change to change the behavior of > Object.prototype.toString on DOM prototypes, then we would roll that out in > two stages: > > 1) Change the class strings on DOM prototype objects, so the > Object.prototype.toString changes (and the Debugger.Object.prototype.class > thing changes too, sadly). > > 2) Add @@toStringTag stuff. > > The idea being to separate breakage from the Object.prototype.toString > changing from breakage from using @@toStringTag instead of class strings to > implement the behavior. > > > -Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
