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

Issue 722790 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression : Unnecessary navigation to chrome://settings page is seen on clicking 'Accessibility settings' icon in Uber Tray

Project Member Reported by mmanchala@chromium.org, May 16 2017

Issue description

Chrome Version: 60.0.3100.0/9556.0.0 dv-channel Daisy,Candy,Minnie and Peppy
OS: Chrome

Pre-Condition : Enable 'Material Design settings' flag from chrome://flags

What steps will reproduce the problem?
(1)Sign into user -> click on Uber Tray -> Select 'Accessibility' option
(2)Now click on 'Accessibility settings' icon-> observe page navigates to chrome://settings page first and then navigates to 'Accessibility' settings section  (Please refer video and screenshot)

Expected: Page should directly navigate to 'Accessibility' settings section on clicking 'Accessibility settings' icon 
Actual: Instead Unnecessary navigation to chrome://settings page is seen 

This is Regression issue as same is working fine for chrome://settings page

@stevenjb : Please confirm the Issue
 
Actual_Navigation.webm
1.3 MB View Download
Actual_SettingsPage-1.png
419 KB View Download
Actual_SettingsPage-2.png
423 KB View Download
Expected_Navigation.webm
1.6 MB View Download
Cc: michae...@chromium.org steve...@chromium.org dpa...@chromium.org
Owner: tbuck...@chromium.org
This is currently expected behavior - we load the settings page then scroll to the correct location. The same thing happens for keyboard/input methods, bluetooth, etc.

tbuckley@ - does the current behavior seem OK to you?


Labels: -Pri-1 Pri-2

Comment 3 by dbeam@chromium.org, May 18 2017

Labels: Hotlist-MD-Settings-Navigation
Owner: scottchen@chromium.org
Status: Started (was: Assigned)
There's a CL for another bug that also addresses this issue: https://codereview.chromium.org/2825203003
Status: Fixed (was: Started)
Status: Verified (was: Fixed)
9649.0.0, 61.0.3129.0

Sign in to add a comment