Regression: Cursor position in search box of chrome://history is not proper after changing the writing direction to 'Right to Left'.
Reported by
jshan...@etouch.net,
Aug 19 2016
|
|||
Issue descriptionChrome Version: 54.0.2832.2 (Official Build)373f6bdd42a605a49fa170b2bcdbae3fbd015acc-refs/branch-heads/2832@{#3}-32/64 bit OS: Mac (10.10.5)(10.11.5), Windows (7,8,8.1,10), Linux(14.04 LTS) Steps: 1. Launch chrome and navigate to chrome://history 2. Right click on Search field and change the writing direction to 'Right to Left'. 3. Observe the cursor. Actual:Position of cursor is not proper after changing the writing direction to'Right to Left' i.e cursor touches R.H.S border of search box. Expected:Position of cursor should be proper after changing the writing direction to 'Right to Left' i.e cursor should not touch R.H.S border of search box. This is regression issue, broken in 'M 54' and below is bisect info: Good build:54.0.2823.0 Bad build:54.0.2824.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/ad8b34b93f28c3c66417d9d15c110f4e77d0c97d..7017637cecdd300f3a90f6afbde474ea4a98a418?pretty=fuller&n=100 Suspecting: r410495 ? Please help to re-assign if your change is not the cause for this issue.
,
Aug 23 2016
tkent@: Could you please take a look at this issue and update accordingly. Note: M-54 branched date is scheduled few days from now. Issue is still reproducible on the latest M-54(54.0.2837.0) as tested on Linux Ubuntu 14.04.
,
Aug 23 2016
In review: https://codereview.chromium.org/2263973002/ BTW, this is very-trivial rendering glitch. This shouldn't block release.
,
Sep 12 2016
Tried the bisect with the new script and was able to narrow down to a single culprit CL. Regression Range ================ https://chromium.googlesource.com/chromium/src/+log/a1e47a8d8e4476467a753f9cadb0436c5fe22d4c..7017637cecdd300f3a90f6afbde474ea4a98a418
,
Sep 14 2016
,
Jan 11
You started fixing this bug over two years ago. Are you still working on it? |
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Aug 19 2016