New issue
Advanced search Search tips

Issue 696492 link

Starred by 1 user
Status: Duplicate
Merged: issue 664679
Owner:
ekaramad@chromium.org
Closed: Feb 2017
Cc:
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

IME jumps unexpectedly while typing under macOS

Reported by antonio....@gmail.com, Feb 27 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Switch keyboard layout Chinese (Simplified) - Pinyin - Simplified
2. Paste the following HTML - <br><br><br><br><br><br><textarea></textarea>
3. Write a few words separated by space in the textarea

What is the expected behavior?
IME popup moves only horizontally to match the position of the character

What went wrong?
IME popup jumps to the top left border of the page from time to time

Did this work before? Yes 55

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.9.5
Flash Version: Shockwave Flash 24.0 r0

Comment 1 by erusev...@gmail.com, Feb 27 2017 

I've experienced the same issue - attached is a GIF that demonstrates the issue.
giphy.gif
70.0 KB View Download

Comment 2 by a...@chromium.org, Feb 27 2017

Components: -UI Blink>Editing>IME UI>Input>Text>IME
Owner: ekaramad@chromium.org
ekaramad, you were working on IME; thoughts?

Comment 3 by ekaramad@chromium.org, Feb 27 2017 

Trying it on 57.0.2987.74 (Official Build) beta (64-bit) I cant repro the same issue. Maybe it has been fixed sine...

I will look at 56 and possibly a bisect to verify if the issue has been fixed on 57.

The bug is possibly due to incorrect composition range (or maybe text selection) updates since I guess those are the kind of states we use in determining the composition options window's position.

Comment 4 by ekaramad@chromium.org, Feb 27 2017 

I also suspect the fix for  issue 664679  which landed past the cut for 56 might have fixed this bug.

Comment 5 by ekaramad@chromium.org, Feb 27 2017

Mergedinto: 664679
Status: Duplicate (was: Unconfirmed)
My guess in comment #4 seems correct. I did a bisect between M56 and M57 to see what fixed it and here is the bisect results:

You are probably looking for a change made after 435673 (known good), but no later than 435701 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/f9409669639beed7cb2859a9e443c3cfad3ea14b..8df2211fda8a25ef28ad268496179e09f77c3c2e

Which includes the fix for  issue 664679 .

This is I believe way too late to merge anything back into M56. But fortunately the issue is fixed on M57.
►

Sign in to add a comment