Regression:Clicking on 'Chrome Settings' link of extension does not navigate to chrome://settings page
Reported by
vineetha...@etouch.net,
May 4 2018
|
||
Issue descriptionChrome Version: 68.0.3419.0 (Official Build)Revision 222512a0ce7deab81dad3af945bad2196e8a8838-refs/heads/master@{#555962}(32/64-bit) OS: Windows(7,8,8.1,10), Linux(14.04 LTS), Mac(10.12.6, 10.13.1, 10.13.5) Test URL: https://chrome.google.com/webstore/search/currently?hl=en-GB What steps will reproduce the problem? (1) Launch Chrome, navigate to above URL and add 'Currently' extension. (2) Open NTP and click on 'Okay, Got it' to activate the extension on NTP (3) Now click on Settings icon of the extension, click on Themes tab and click on 'Chrome Settings' link and observe. Actual Result: Clicking on 'Chrome Settings' link of extension does not navigate to chrome://settings page. Expected Result: Clicking on 'Chrome Settings' link of extension should navigate to chrome://settings page. This is regression issue broken in ‘M-61’ and providing the bisect using per-revision bisect, Good build: 61.0.3125.0(Revision: 478136) Bad build: 61.0.3126.0(Revision: 478483) You are probably looking for a change made after 478469 (known good), but no later than 478470 (first known bad). CHANGE-LOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/2410fc6b7d05f26bca8b649aded31e959060ea3b..fbc499463c31aaa00a4180d11ec348a12650065b Suspect: https://chromium.googlesource.com/chromium/src/+/fbc499463c31aaa00a4180d11ec348a12650065b @dbeam: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note : As @dbeam is no longer in Chrome adding @wychen in cc. Thank You!
,
May 5 2018
The extension in question is making the following call
chrome.tabs.update({url: 'chrome://chrome/settings'})
Instead it should call
chrome.tabs.update({url: 'chrome://settings'})
I don't think there is anything to be fixed on the Chrome side.
|
||
►
Sign in to add a comment |
||
Comment 1 by dbeam@chromium.org
, May 5 2018Owner: ----