New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 673200 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Screen magnifier moves focus to the caret when an irrelevant window has moved.

Project Member Reported by kinaba@chromium.org, Dec 12 2016

Issue description

Chrome Version: 57.0.2949.0
OS: ChromeOS 9049.0

What steps will reproduce the problem?
(1) Enable "Screen Magnifier" in the accessibility settings.
(2) Focus the ombibox of a Chrome browser window.
(3) Move the mouse cursor, click the task tray (the clock ~ profile icon) to show the menu.

What is the expected result?
The menu opens and shows up.

What happens instead?
The menu opens and shows up, and the magnified screen moves back to the omnibox, putting the opened menu out of display.




The bug is more visible when ARC apps are in use (b/33491318), where the mouse cursor surface generated inside Android is represented as an aura window, so all mouse movement over an ARC window triggers magnifer refocusing.
 

Comment 1 by kinaba@chromium.org, Dec 12 2016

Cc: osh...@chromium.org jen...@chromium.org

Comment 2 by kinaba@chromium.org, Dec 12 2016

Labels: M-55

Comment 3 by kinaba@chromium.org, Dec 13 2016

Cc: hannia@chromium.org
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 14 2016

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

commit c0105686d120fe7978122cf399061c738de15134
Author: kinaba <kinaba@chromium.org>
Date: Wed Dec 14 00:04:52 2016

Ash magnifier: Check whether the caret bounds were actually moved or not.

If the caret bounds were not actually moved, do not move the magnification
window. Otherwise it causes unnecessary move of focuses.

BUG= 673200 
TEST=MagnificationControllerTest

Review-Url: https://codereview.chromium.org/2562273002
Cr-Commit-Position: refs/heads/master@{#438347}

[modify] https://crrev.com/c0105686d120fe7978122cf399061c738de15134/ash/magnifier/magnification_controller.cc

Comment 5 by kinaba@chromium.org, Dec 14 2016

Fixed on trunk. After waiting for the canary image, I'll start request merging.

Comment 6 by kinaba@chromium.org, Dec 15 2016

Labels: Merge-Request-56

Comment 7 by dimu@chromium.org, Dec 15 2016

Labels: -Merge-Request-56 Merge-Approved-56 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M56 (branch: 2924)
Project Member

Comment 8 by bugdroid1@chromium.org, Dec 15 2016

Labels: -merge-approved-56 merge-merged-2924
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c8221d1bf74e1b1951322795f93b1fc93a62044e

commit c8221d1bf74e1b1951322795f93b1fc93a62044e
Author: Kazuhiro Inaba <kinaba@chromium.org>
Date: Thu Dec 15 04:02:10 2016

Ash magnifier: Check whether the caret bounds were actually moved or not.

If the caret bounds were not actually moved, do not move the magnification
window. Otherwise it causes unnecessary move of focuses.

BUG= 673200 
TEST=MagnificationControllerTest

Review-Url: https://codereview.chromium.org/2562273002
Cr-Commit-Position: refs/heads/master@{#438347}
(cherry picked from commit c0105686d120fe7978122cf399061c738de15134)

Review-Url: https://codereview.chromium.org/2572413002 .
Cr-Commit-Position: refs/branch-heads/2924@{#507}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}

[modify] https://crrev.com/c8221d1bf74e1b1951322795f93b1fc93a62044e/ash/magnifier/magnification_controller.cc

Comment 9 by kinaba@chromium.org, Dec 15 2016

Labels: Merge-Request-55
Summary: Screen magnifier moves focus to the caret when an irrelevant window has moved. (was: Screen magnigier moves focus to the caret when an irrelevant window has moved.)
Requesting M55 merge too.

The bug makes the accessibility feature (screen magnifier) almost unusable for ARC apps and is leading to a very bad UX for people relying on the feature,
while the fix https://codereview.chromium.org/2562273002 is simple and safe.
Labels: -Hotlist-Merge-Approved -Merge-Request-55 -merge-merged-2924
Labels: Merge-Request-55

Comment 12 by dimu@chromium.org, Dec 16 2016

Labels: -Merge-Request-55 Merge-Review-55 Hotlist-Merge-Review
[Automated comment] Request affecting a post-stable build (M55), manual review required.
Cc: bhthompson@chromium.org
ping: TPM.
Labels: -Hotlist-Merge-Review -Merge-Review-55 Merge-Approved-55
Sorry for not seeing this earlier, we can land this, however we don't plan on any further 55 pushes, 56 goes stable at the end of the month though.
Project Member

Comment 15 by bugdroid1@chromium.org, Jan 10 2017

Labels: -merge-approved-55 merge-merged-2883
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/de251a2ef1fefabae9a14ec520a5ca2c1aafe6d8

commit de251a2ef1fefabae9a14ec520a5ca2c1aafe6d8
Author: Kazuhiro Inaba <kinaba@chromium.org>
Date: Tue Jan 10 01:51:41 2017

Ash magnifier: Check whether the caret bounds were actually moved or not.

If the caret bounds were not actually moved, do not move the magnification
window. Otherwise it causes unnecessary move of focuses.

BUG= 673200 
TEST=MagnificationControllerTest

Review-Url: https://codereview.chromium.org/2562273002
Cr-Commit-Position: refs/heads/master@{#438347}
(cherry picked from commit c0105686d120fe7978122cf399061c738de15134)

Review-Url: https://codereview.chromium.org/2623773002 .
Cr-Commit-Position: refs/branch-heads/2883@{#755}
Cr-Branched-From: 614d31daee2f61b0180df403a8ad43f20b9f6dd7-refs/heads/master@{#423768}

[modify] https://crrev.com/de251a2ef1fefabae9a14ec520a5ca2c1aafe6d8/ash/magnifier/magnification_controller.cc

Status: Fixed (was: Started)
Thanks. Did the merge only just in case, then.
Status: Verified (was: Fixed)

Sign in to add a comment