Issue metadata
Sign in to add a comment
|
Regression : Settings button ('Gear' icon) doesn't work in ''Panda Safe Web' extension.
Reported by
avsha...@etouch.net,
Oct 12 2017
|
||||||||||||||||||||||
Issue descriptionChrome version : 63.0.3238.0 (Official Build) fc7c1e473dfde53eb32f2e6528d6b0f957f850f5-refs/heads/master@{#508208} 32/64 bit OS : Windows(7,8,10), Mac(10.12.6) Test URL : https://chrome.google.com/webstore/detail/panda-safe-web/fagakgcelolinfnkfgekcnedpaklfcok What steps will reproduce the problem? 1. Launch chrome, navigate to test URL and install 'Panda Safe Web' extension. 2. Open NTP, navigate to any web page (Ex. www.google.com) and click on ''Panda Safe Web' extension icon seen on the chrome toolbar (extension dialog opens). 3. Now click on 'Gear' icon seen at the bottom of extension dialog and observe. Actual Result : Settings button ('Gear' icon) doesn't work in ''Panda Safe Web' extension. Expected Result : Settings button should work and it should navigate to extension's settings page. This is a regression issue broken in ‘M-59’ and using the per-revision bisect providing the bisect results, Good build : 59.0.3064.0 (Revision : 462306) Bad build : 59.0.3065.0 (Revision : 462712) You are probably looking for a change made after 462413 (known good), but no later than 462414 (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/7773939ef302371795ef39138e10225f3d493aa1..c7d27da6abdf2bb847539a83e485e7d0389ccce0 Suspect : https://chromium.googlesource.com/chromium/src/+/c7d27da6abdf2bb847539a83e485e7d0389ccce0 @eustas : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner. Note : Unable to reproduce issue on Linux(14.04 LTS) OS since 'Panda Safe Web' extension doesn't function properly on Linux. Thank you. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by eustas@chromium.org
, Oct 12 2017Works as intended. Extension violates HTTP protocol. Server is eligible to send response only in advertised encodings ("accept-encoding" header"). But it ignores and always sends with "content-encoding: br". "br" is advertised only over https connection to avoid problems with proxies.