Are we still concerned about compatibility issues caused by this? Regards, Florin.
-----Original Message----- From: dev-platform [mailto:dev-platform-bounces+florin.mezei=softvisioninc...@lists.mozilla.org ] On Behalf Of Boris Zbarsky Sent: Monday, June 06, 2016 11:30 PM To: dev-platform@lists.mozilla.org Subject: Re: Intent to implement and ship: Changing the toString result on DOM prototype objects On 6/3/16 11:41 AM, Boris Zbarsky wrote: > * Chrome: has been shipping the behavior I'm proposing to change to > since Chrome 50, I believe. Current Chrome release version is 51. One note: earlier versions of Chrome claimed [object Object] for DOM prototypes. So the claim the Google folks are making is that returning [object FooPrototype] is not needed for web compat. > Possible alternatives: We could make @@toStringTag an accessor on the > prototype that returns different things for instances and the > prototype itself. The hard part here is convincing the Chrome folks. -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
