- From: <bugzilla@jessica.w3.org>
- Date: Tue, 17 Mar 2015 15:31:53 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776 --- Comment #27 from David Dorwin <ddorwin@google.com> --- I think we are in agreement that these examples should be reported via key status. The remaining question is how to report the system codes in a way that discourages applications from depending on them and/or changing behavior based on them. See also comment #20. One proposed solution is to put text in the spec telling applications that the values could change over time and not to depend on them. Another possible solution would be to provide a getter that returns a sequence of system codes (or add an attribute that is a sequence of system codes). In this case, the application could check the getter (or attribute) at any time, including on a keystatuseschange event, after a playback error, or before disposing of the session object. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 17 March 2015 15:31:56 UTC