1940574 - intl_keyboard_layout data is inconsistent

Status: ASSIGNED

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[Tom Ritter [:tjr]]

Attachment: Untitled.png

Wile validating the data from our set of volunteers, I found that the data we are getting for intl_keyboard_data is inconsistent across OS. We could probably apply a mapping on the backend to correct and unify the desktop OS values, but Android seems not to report anything at all. Is that because the keyboard layout is a function of a different language setting? If so, we can use that setting in the backend mapping as well.

Comment 1

[Fatih Kilic [:fkilic]]

We probably should do it but there isn't a comprehensive list of keyboard layouts. Windows provides this https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-language-pack-default-values, but there isn't anything available for MacOS, wayland and x11 afaict. I'll take a look at android and see if something can be done but apparently there's no reliable way of doing this on android (some report specific keyboards, e.g. google keyboard, just return empty string)

Comment 2

[Fatih Kilic [:fkilic]]

Attachment: Bug 1940574: Consider using kTISPropertyInputSourceID instead of kTISPropertyLocalizedName. r?tjr

Instead of returning localized layout names, we may consider using "reverse DNS name associated with the input source"

Comment 3

[Fatih Kilic [:fkilic]]

Attachment: Bug 1940574: Implement nsLookAndFeel::GetKeyboardLayoutImpl on Android. r?tjr

Comment 4

[Phabricator Automation]

Comment on attachment 9446681 [details]
Bug 1940574: Implement nsLookAndFeel::GetKeyboardLayoutImpl on Android. r?tjr

Revision D233762 was moved to bug 1940840. Setting attachment 9446681 [details] to obsolete.

Comment 5

[Phabricator Automation]

Comment on attachment 9446555 [details]
Bug 1940574: Consider using kTISPropertyInputSourceID instead of kTISPropertyLocalizedName. r?tjr

Revision D233667 was moved to bug 1940840. Setting attachment 9446555 [details] to obsolete.