This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25746 - 14.3.3 - how should remote end determine current keyboard locale?
Summary: 14.3.3 - how should remote end determine current keyboard locale?
Status: RESOLVED INVALID
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-05-16 21:29 UTC by Andrey Botalov
Modified: 2016-09-19 16:18 UTC (History)
3 users (show)

See Also:

Attachments

Description Andrey Botalov 2014-05-16 21:29:07 UTC 
14.3.3 section contains phrases:
> The keys considered upper-case symbols are either defined by the current keyboard locale

> the implementation should use the current keyboard locale to determine which symbols are upper case

I think that means that remote end should determine current keyboard locale. But it's not clear how remote end can say current keyboard locale without local end saying locale to it.
Comment 1 Andreas Tolfsen 2014-05-19 13:40:22 UTC 
So my impression was that we weren't going to rely on locale, but instead assume a traditional US English keyboard layout?  I'm struggling to see how we can implement it otherwise.