- From: <bugzilla@jessica.w3.org>
- Date: Wed, 25 Feb 2015 22:06:55 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776 --- Comment #25 from David Dorwin <ddorwin@google.com> --- Jerry has an action to provide more information about the use cases he is targeting with this event and which object it should be fired at. Comments in the meantime: * It's unclear if the latest proposal solves the logging use case. * Many of the use cases for system code logging are related to keystatuses, which already has a separate event. * Others result in rejected promises. - Note: Chrome is currently appending the system code to the DOMException's message. * Some of the use cases may be covered by and/or better discussed in bug 27067. * There are reasons to avoid an event (see comment 20). While a string provides some level of disincentive to make application decisions, it is still possible and less useful than a numeric value. I believe we agreed not to subclass Error. Among other things, we might need to define our own script bindings. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 25 February 2015 22:06:58 UTC