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

[Bug 28244] Requiring @@toStringTag on instances may have performance implications

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Dec 2016 18:38:36 +0000
To: public-script-coord@w3.org
Message-ID: <bug-28244-3890-NBqs37DISF@http.www.w3.org/Bugs/Public/>

Rick Byers <rbyers@chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |rbyers@chromium.org

--- Comment #18 from Rick Byers <rbyers@chromium.org> ---
> As long as there is divergence, one engine or another will see a lot of noise in idlharness.js tests in web-platform-tests, making it harder to spot real issues (more tooling would help, we're trying that too).

I haven't fully parsed the whole history here, but I agree getting consensus on
this is important to IDL tests.  Is there any work / data the Chrome team could
provide that would help with the compat argument?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 16 December 2016 18:38:46 UTC

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