Re: [w3c/uievents-code] Need an implementation report (#20)

Back before -key and -code were extracted from UIEvents, There were tables (many from other industry specs) that covered media keys so that those devices would be covered by the spec if those keys were present.

We've made use of some of these values for multimedia keyboards, and we expect that some browsers (e.g., browsers on TVs) would make use of a wider set of these values. Because this is a long tail of different products, we wanted to make sure that we had something specified so that manufacturers don't make up their own values for these keys.

The implementation report, however, only covers major browsers since those are the only implementations we're aware of.

We basically have 2 options:
(1) Remove values that aren't already being used on a major desktop browser and hope that the "long tail" of embedded browsers use consistent values.
(2) Keep them in the spec so that future products have consistent values, but recognize that not all of them are currently used.

Up 'til now, we've opted for (2), since it seems more future-proof. But I can understand the argument for (1).


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents-code/issues/20#issuecomment-369396228