Issue metadata
Sign in to add a comment
|
Regression: Proxy authentication dialog doesn't stay when chromevox is enabled |
||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3112.66 OS: Ubuntu 14.04,Windows Pre-Condition: Make sure proxy is enabled What steps will reproduce the problem? (1)After enabling proxy open chrome and add chromevox extension (2)Now restart chrome and try navigating to any other page and observe for proxy authentication dialog Expected: Proxy authentication bubble should stay even when chromevox is enabled. Actual: Instead Proxy authentication bubble vanishes immediately after navigating to any page and hence unable to browse further. This is a regression issue broken in M58. Good Build: 57.0.2987.0 dev Bad Build: 58.0.2988.0 dev
,
Jul 12 2017
Getting an error while bisecting with proxy. Attaching screenshot of same. Hence providing manual bisect info and changelog from omahaproxy Manual Bisect Info: ==================== Good Build: 57.0.2987.0 dev Bad Build: 58.0.2988.0 dev CL: https://chromium.googlesource.com/chromium/src/+log/57.0.2987.0..58.0.2988.0?pretty=fuller&n=10000 Suspecting https://codereview.chromium.org/2474323002 from changelog @avallee: Please pardon me if it has nothing to do with your change, and please help in assigning to appropriate owner.
,
Jul 13 2017
Bisect script doesn't work with proxy enabled. Hence updating narrowed bisect info. Good Build: 57.0.2987.154 Bad Build: 58.0.2988.0 CHANGELOG URl: https://chromium.googlesource.com/chromium/src/+log/57.0.2987.154..58.0.2988.0?pretty=fuller&n=10000
,
Jul 13 2017
What proxy are you using to test this?
,
Jul 13 2017
I just checked out and rebuilt 58.0.2988.0. I tested by running this simple proxy https://gist.github.com/avallee/8f22638a8d8272b20e70ce11656ffc4c on my machine and using the flag --proxy-server=localhost:8888 I tried both with and without my change on linux and was not able to reproduce.
,
Jul 20 2017
,
Jul 25 2017
Nope, this is not the same. In that case, the issue was related to the sign-in dialog, which is not presented here.
,
Aug 30 2017
,
Dec 15 2017
,
Dec 17
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
,
Dec 21
Assigning to dmazzoni@ for chromevox triage (though perhaps this is no longer an issue) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Jul 12 2017