New issue
Advanced search Search tips

Issue 921202 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 918537



Sign in to add a comment

SingleProcessMash: dvorak keyboard layout is entirely broken on nocturne

Project Member Reported by aaboagye@chromium.org, Jan 11

Issue description

I just installed a 11558.0.0 test image on my nocturne and the dvorak keyboard layout is entirely broken. I'm not even sure what layout it thinks it is. QWERTY seems fine though.

here's the homerow:
ar.gcedybo

it's completely wrong, it should be
aoeuidhtns-

Here's a feedback report I filed: http://shortn/_wfCiWHFnE8
 
Cc: afakhry@chromium.org
afakhry@ do you know who might know about physical keyboard layouts?
Cc: shuchen@chromium.org yhanada@chromium.org kpschoedel@chromium.org
Re #1: shuchen@, yhanada@ or kpschoedel@ should know.
Drive-by: That version has the new sysui SingleProcessMash feature enabled. Could you try turning it off in about:flags?

If the problem goes away, please assign the bug to me and I'll route it. Otherwise, the people in #2 seem right.
Owner: jamescook@chromium.org
Hey James, yes, disabling that flag restored the correct dvorak layout.
Blocking: 918537
Cc: steve...@chromium.org xiy...@chromium.org msw@chromium.org
Labels: Proj-Mash-SingleProcess
Owner: ----
Summary: SingleProcessMash: dvorak keyboard layout is entirely broken on nocturne (was: nocturne: 11558.0.0 dvorak keyboard layout is entirely broken)
xiyuan/msw/stevenjb - IME issue? Event rewriter issue?

aaboagye: I just reverted SingleProcessMash on Chrome ToT, so the next uprev should fix this problem for you.

Thanks so much!
Cc: derat@chromium.org dtapu...@chromium.org
 Issue 919271  has been merged into this issue.
Owner: sky@chromium.org
Status: Started (was: Untriaged)
Cc: michae...@chromium.org
I explained the weirdness in  issue 919271 . It's like the keys are being translated *twice* instead of just once:

  "asdf" => "aoeu" => "ar.g"

  QWERTY "asdf" == Dvorak "aoeu"
  QWERTY "aoeu" == Dvorak "ar.g"
You are exactly right that the map is applied twice.
Project Member

Comment 12 by bugdroid1@chromium.org, Jan 18 (4 days ago)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1

commit 154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1
Author: Scott Violet <sky@chromium.org>
Date: Fri Jan 18 20:47:52 2019

Modernize Mojo serialization of ui::KeyEvents

This changes serialization to write key_code, dom_code, dom_key and whether it's
a character. These four things are the key properties that identify a KeyEvent.
The previous code would result in potentially applying keyboard layouts to the
deserialized event, which is problematic if the layout was already applied
before serialization.

BUG= 921202 
TEST=covered by tests

Change-Id: I7a15ed2fce6e084988b8f23bbf2f06f420ff3771
Reviewed-on: https://chromium-review.googlesource.com/c/1409461
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#624269}
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/chrome/browser/chromeos/preferences.h
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/event.cc
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/event.h
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/event_constants.h
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/keycodes/dom/dom_key.h
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/mojo/event.mojom
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/mojo/event_struct_traits.cc
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/mojo/struct_traits_unittest.cc
[modify] https://crrev.com/154ad7d65aa5ad38dd1ce19ee1c4cc9cb799c9a1/ui/events/ozone/layout/keyboard_layout_engine_manager.cc

Comment 13 by sky@chromium.org, Jan 18 (4 days ago)

Status: Fixed (was: Started)

Sign in to add a comment