Re: Mapping between DOM3 keylist and CEA2014/OIPF virtual keycodes

What I'm trying to do is to map each CEA2014 "virtual key code" to a DOM3
"key value". This is useful in various cases, e.g.

- for devices that have to implement both the old and the new model
- for app developers that are moving their apps to html5 from ce-html and
want to replace they key handling code.

As the DOM3 spec value list was generated considering also CEA2014, all
values in dom3 should have an equivalent there, so I'm just trying to make
it explicit. The fact that I'm missing the back key is strange.

Is the spec you mention a mapping on DOM3 spec? How do you map the
return/back key?




On Tue, Aug 13, 2013 at 5:47 PM, Clarke Stevens <C.Stevens@cablelabs.com>wrote:

>  I'm not sure where you're going with this, but CableLabs has a remote
> key mapping spec for cable boxes if you want to look at that.
>
>  -Clarke
>
> Sent from my iPad
>
> On Aug 13, 2013, at 1:46 AM, "Giuseppe Pascale" <giuseppep@opera.com>
> wrote:
>
>   Hi all,
> I was trying to map the key values in DOM3 spec [1] with the ones defined
> by CEA2014
> The result is attached. I was wondering if people on this list with
> relevant knowledge (Glenn, Mark, Bob, Doug, I'm looking at you ;) ) could
> check it and see if it they agree on the mapping.
>
>  In particular, I have an issue with the "back" key: CEA2014 have both a
> "VK_BACK" and VK_BACK_SLASH". The latter maps on DOM3 "Backspace" but what
> about the first?
>
>  (VK_BACK is the "return" key you find on many TV remote controllers)
>
>  cheers,
> /g
>
>  [1]
> http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/#key-values-list
>
>
>
>
>
>    <keymapping.html>
>
>