New issue
Advanced search Search tips

Issue 784901 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

typing buffer in chrome does not respect where cursor is pointing/what is highlighted

Reported by jeffrey....@gmail.com, Nov 14 2017

Issue description

Chrome Version: 	64.0.3261.0 (Official Build) dev (64-bit)
Chrome OS Version: 	10106.0.0 (Official Build) dev-channel terra
Chrome OS Platform:  Asus C202S
Network info: (all networks)

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) make new tab with this ( https://bugs.chromium.org/p/chromium/issues/entry?template=Defect%20on%20Chrome%20OS ) 'new bug' template
(2) type "typing buffer" only start with an n "ntyp", control-left after  typing 'p'. delete the n control-right to get to the end of the word type 'e' note that the n returns

Expected Result:
if i've deleted the 'n' it shouldn't come back when i type at the end of the word

Actual Result:
the n returns

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

not just always on the above steps but often when i make typos. Letters appear,  words are clobbered by what i'm typing,  the cursor jumps to incorrect positions, and punctuation does not appear even if i hit the key to insert a punctuation (ie ".") unless i use the arrow keys to move to a new position.  

What is the impact to the user, and is there a workaround? If so, what is
it?

makes it very frustrating to type. This does not seem to have affected me with beta / stable, just dev channel.


Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
turned off Auto-correction (in the US Dvorak Keyboard (English Settings) page), next word prediction and auto capitalization, and that made all the difference. Seems to work much better now.

Comment 2 by vsu...@chromium.org, Jan 16 2018

Components: UI>Input>Text
Owner: shuchen@chromium.org
Status: Assigned (was: Unconfirmed)
shuchen, not sure who works on this. Please triage.
Cc: shuchen@chromium.org
Owner: wuyingbing@chromium.org
This seems related to the PKA (Physical Keyboard Auto-correction) feature in the IME extension.

Yingbing, can you please take a look? Thanks.

Labels: -Pri-3 Pri-2
Status: WontFix (was: Assigned)
Not repro

Sign in to add a comment