New issue
Advanced search Search tips

Issue 885067 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

hp 13 g1 (chell) german keyboard: ^ + space = ² (should be ^)

Project Member Reported by anj@google.com, Sep 18

Issue description

Chrome Version: 68.0.3440.118 (Offizieller Build) (64-Bit)
Chrome OS Version: 10718.88.2 (Official Build) stable-channel
Chrome OS Platform: chell
Network info: not relavant to keyboard issues

Steps To Reproduce:
(1) Take a HP 13 G1 (chell) with german keyboard and configure it to use the normal german key map.
(2) Press ^ (which is a dead key) followed by space

Expected Result: ^ character

Actual Result: ² character

How frequently does this problem reproduce? Always, verified on several machines.

Workaround: press ^ twice to get a single ^ character.

For other dead keys like ` and ´: they can be used with both pressing that key twice, or with following up with a space char. So to me ^ + space should give me a ^. Also alt-gr + 2 = ², so there is no need for that character to be available through any other means.

Unless we can provide high visibility about the workaround, I think users will be unhappy. I didn't find it myself, nor did techstop.
 
Components: UI>Input>Text
Cc: afakhry@chromium.org shuchen@chromium.org kpschoedel@chromium.org
Components: -UI>Input>Text UI>Input>Text>IME
Status: Untriaged (was: Unconfirmed)
Looks like an outright mistake in character_composer_sequences.txt:

  Dead<combining circumflex accent> <space> <^>
  Dead<combining circumflex accent> <space> <superscript two>

There should never be two entries with identical LHS, and the second one (which wins) doesn't make sense.

I'll submit the fix right away since it's trivial.

Cc: -kpschoedel@chromium.org
Owner: kpschoedel@chromium.org
Status: Started (was: Untriaged)
Thanks, kevin. Assigning to you.
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 29

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

commit 9f27e4a30e76a1b5a49e1d307c7c989000ffd34f
Author: Kevin Schoedel <kpschoedel@chromium.org>
Date: Mon Oct 29 14:14:45 2018

Remove spurious key composition [circumflex][space]->[²]

The composition sequences included the above incorrect mapping
as well as the correct [circumflex][space]->[^].

Bug:  885067 
Test: none
Change-Id: I3144ede559dc66184ecae0ab1ef032a7ba067946
Reviewed-on: https://chromium-review.googlesource.com/c/1302497
Reviewed-by: Shu Chen <shuchen@chromium.org>
Commit-Queue: Kevin Schoedel <kpschoedel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#603485}
[modify] https://crrev.com/9f27e4a30e76a1b5a49e1d307c7c989000ffd34f/ui/base/ime/chromeos/character_composer_data.h
[modify] https://crrev.com/9f27e4a30e76a1b5a49e1d307c7c989000ffd34f/ui/base/ime/chromeos/character_composer_sequences.txt

Status: Fixed (was: Started)

Sign in to add a comment