Regression:Google logo does not get change on using extension 'nyoogle'
Reported by
shruti.j...@etouch.net,
Jan 11 2018
|
|||
Issue descriptionChrome Version: 65.0.3318.0(Official Build)Revision 193c7425ab494d87b07d70a1df512d58fcd58b58-refs/heads/master@{#528541}(32/64 Bit) OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1,10.13.3) Test URL: https://chrome.google.com/webstore/detail/nyoogle-custom-logo-for-g/ginfoagmgomhccdaclfbbbhfjgmphkph Steps to reproduce: 1.Launch Chrome, go to chrome://apps. 2.Add extension 'nyoogle' from above mentioned test url and click on option of added extension in omnibox. 3.Click on "Never show google special logos" and go to NTP and observe. Actual Result: In NTP, Google logo does not get change on using extension 'nyoogle'. Expected Result: Google logo should change on using extension 'nyoogle'. This is regression issue broken in ‘M-61’ and below per-revision bisect result: Using the per-revision bisect providing the bisect results, Good Build: 61.0.3160.0(Revision:487323) Bad Build: 61.0.3161.0(Revision:487694) You are probably looking for a change made after 487663 (known good),but no later than 487664 (first known bad). CHANGELOG 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/239b085ef005c805d2b85daeadd600e9fec61e1a..993682e9e2b181a14f9fd9e6a7f848e401a551e7 Suspect: https://chromium.googlesource.com/chromium/src/+/993682e9e2b181a14f9fd9e6a7f848e401a551e7 @rdevlin.cronin: 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: This issue is also seen on M-63 Stable (build #63.0.3239.132),M64 Beta(build #64.0.3282.85) ,M65 Dev(build #65.0.3315.3). Thank You!
,
Jan 11 2018
This is working as intended. Extensions wishing to modify the NTP should use the chrome_url_overrides API. Scripting the NTP is no longer allowed.
,
Feb 2 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Jan 11 2018