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

Issue 862574 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: 'Keyboard' and 'Accessibility' options are not getting reflected automatically at Uber Tray

Project Member Reported by mmanchala@chromium.org, Jul 11

Issue description

Chrome Version: 69.0.3480.0/10865.0.0 dev channel  Peach-pit,Celes and Swanky
OS: Chrome

What steps will reproduce the problem?
(1)Recover build ->In sign in screen enter valid Email and Password -> after signing in immediately click on Uber Tray -> Observe Network, Bluetooth, Notifications & Night light options are seen
(2)Do not close Uber Tray for 2- 3 min  -> observe still 'Keyboard' and 'Accessibility' options are not available at Uber Tray and able to see this options again after closing and opening Uber tray 

Expected: 'Keyboard' and 'Accessibility' options should get reflect automatically at Uber Tray
Actual: Instead 'Keyboard' and 'Accessibility' options are not getting reflected automatically at Uber Tray 

This is Regression Issue as same is working fine in M-68
 
Actual_Options.mp4
19.8 MB Download
Attaching Expected video for reference
Expected_Options.mp4
17.6 MB Download
Labels: -Type-Bug -Pri-2 Pri-1 Type-Bug-Regression
Cc: -ajha@chromium.org -tbuck...@chromium.org yoshiki@chromium.org
Owner: yamaguchi@chromium.org
Status: Assigned (was: Untriaged)
Status: Started (was: Assigned)
Status: Assigned (was: Started)
Labels: -M-69 M-70
Punting to M-70, because the unified system tray (the new Uber Tray) will not be enabled by default until M70.
Cc: yamaguchi@chromium.org
Owner: toshikikikuchi@google.com
Toshiki's last starter bug.
Status: Started (was: Assigned)
The following revision can fix the keyboard option issue.
  https://chromium-review.googlesource.com/c/chromium/src/+/1161703
However, the accessibility option issue is more complex.
The problem is that ShouldShowAccessibilityMenu() method returns the previous status *right after* changing the accessibility settings via accessibility controller. There is a little delay.
Cc: tbuck...@chromium.org ajha@chromium.org
 Issue 867369  has been merged into this issue.
Project Member

Comment 11 by bugdroid1@chromium.org, Aug 8

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

commit 85a051c1a9e398be644bde8457cf1cf4438fad03
Author: Toshiki Kikuchi <toshikikikuchi@google.com>
Date: Wed Aug 08 00:26:26 2018

Add IME observer to IME button

Adding IME status observer to the IME button in the unified system tray. In
previous implementation, the visibility of the button is not updated automatically when the IME status is changed.

TEST=IMEFeaturePodControllerTest
BUG=862574

Change-Id: I41d3ef6085b165bb1f3e3d165a0369779d424ad7
Reviewed-on: https://chromium-review.googlesource.com/1161703
Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Toshiki Kikuchi <toshikikikuchi@google.com>
Cr-Commit-Position: refs/heads/master@{#581413}
[modify] https://crrev.com/85a051c1a9e398be644bde8457cf1cf4438fad03/ash/BUILD.gn
[modify] https://crrev.com/85a051c1a9e398be644bde8457cf1cf4438fad03/ash/system/ime/ime_feature_pod_controller.cc
[modify] https://crrev.com/85a051c1a9e398be644bde8457cf1cf4438fad03/ash/system/ime/ime_feature_pod_controller.h
[add] https://crrev.com/85a051c1a9e398be644bde8457cf1cf4438fad03/ash/system/ime/ime_feature_pod_controller_unittest.cc

Status: Assigned (was: Started)

Sign in to add a comment