Re: About KeyboardEvent.keylocation property for TV/STB

I think a good argument could be made to use DOM_KEY_LOCATION_MOBILE for keys from remote controls. For one thing, a traditional remote control device fits the definition:

> DOM_KEY_LOCATION_MOBILE
> The key activation originated on a mobile device, either on a physical keypad or a virtual keyboard.

Second, in current widespread practice, remote control functionality comes from both traditional dedicated remote control devices as well as apps running on phones and tablets. Since they are performing the same function, treating them the same makes sense.

Thanks,
mav

On Aug 27, 2013, at 2:43 PM, Giuseppe Pascale <giuseppep@opera.com>
 wrote:

> Hi,
> I don't think there is any TV/STB out there using DOM3 events model,
> although there may be in future. (depends also at what kind of
> enviroment you are looking at, web technologies are used in many
> different ways inside TVs and STBs)
> 
> About TV specific extensions or in general the value that keylocation
> will take in case of TV implementations I think this is a good point.
> It could be raised with the DOM group but is also a question for
> implementers and also for TV groups (like DLNA or HbbTV) that could
> influence that by mandating a special value in some cases.
> 
> I would guess that missing a dedicated value and a reason for doing it
> most implementers will just use "DOM_KEY_LOCATION_STANDARD"
> 
> 
> 
> On Wed, Aug 21, 2013 at 6:59 AM, Arunprasad Rajkumar
> <ararunprasad@gmail.com> wrote:
>> Hello Folks,
>> 
>> Is there any way to use KeyboardEvent.keylocation in TV/STB world to
>> differentiate keys originating from Remote Control & Front Panel?
>> 
>> Stable DOM 3 Event specification doesn't have any DOM_KEY_LOCATION constants
>> for TV/STB. Is there any plan for adding more constants(relevant to TV) in
>> upcoming specs(may be DOM 4 Events) ?
>> 
>> Regards,
>> Arun
>

Received on Tuesday, 27 August 2013 22:09:14 UTC