Images on image.google.com wont expand if page is secure |
|||
Issue descriptionChrome Version: M57+ OS: All What steps will reproduce the problem? (1) Visit images.google.com (2) Search for a test image (firefox) (3) Click to expand an image What is the expected result? Images should expand when user clicks on it. Given that this is google.com page, it should stay secure. What happens instead? Clicking on an image does not expand the image and Page switches to un-secure as soon as image expands. I can replicate this behaviour in incognito as well. This could be a search issue but other users claim that they don't experience this issue on other browsers. Screenshot and Net-Internal logs attached Forum : https://productforums.google.com/forum/#!topic/chrome/WI4NhHDPJlQ I was able to replicate this issue as well.
,
Feb 7 2017
+1 to what davidben said, however it looks like some users aren't able to expand the images in the first place which means we are hard-blocking them? I'm unable to repro the issue with a Win10 machine and Norton Identity Safe extension mentioned by the reporter.
,
Feb 7 2017
Hrm. If they're not able to expand them at all, we could get a net-internals from them per https://dev.chromium.org/for-testers/providing-network-details and poke at it. But if it's somehow correlated with antivirus and stuff, the antivirus is probably just messing things up. They tend to do that.
,
Feb 8 2017
,
Feb 8 2017
This issue on image.google.com was fixed by Search team through P0 bug b/34771082. While image wont open issue is fixed, but issue where page turns unsecure is still relevant. After you get search results, clicking on few images would turn page unsecured.
,
Feb 8 2017
The page changing state is working as intended. It would be a bug if it didn't, given that the page is doing. See comment #1. To get that changed would not be a change in Chrome, but a change in Search. Given the other issue has been fixed, I think we can WontFix this?
,
Feb 8 2017
I agree, this is working as intended now that the other bug is fixed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by davidben@chromium.org
, Jan 27 2017Labels: Team-Security-UX