Setting default browser as bing causes image search to have non-functional options
Reported by
si...@codeaurora.org,
Apr 26 2016
|
||
Issue descriptionSteps to reproduce the problem: 1. Open up chrome browser, go into settings. Make sure the option "Merge tabs and apps" option is turned off. Then, go into search engine, and set the default engine to Bing. 2. Search for any image by entering it into the omnibox. In my example I will search "cat" 3. Tap an image in the search results to expand the image, and tap the arrow on the bottom right to open up the options menu. 4. Tap the "source image" button in the options menu. What is the expected behavior? The source image should open up in the browser and be displayed. What went wrong? Instead of the source image being displayed, it goes back and displays the results page with all of the results images blurred. Did this work before? N/A Chrome version: 49.0.2623.105 Channel: stable OS Version: Flash Version: Shockwave Flash 21.0 r0 This issue does not occur if you navigate to bing.com manually or if you refresh the page once you are at the results page. You must get to the results page by using the ominibox search to reproduce this. The attached files show the search results page and the image options page, as well as the actual and expected outputs.
,
May 10 2016
This is a problem with bing. When you try to load the image, the following is printed to the console: /images/search?q=cat&view=detailv2&&id=E14DBA5A1D6082E2E7F86A25518BACAE1C00…085359&thid=OIP.M7cf9f637bad11855cde346ba3f8cddb1H0&PC=U316&mode=overlay:1 Mixed Content: The page at 'https://www.bing.com/images/search?q=cat&view=detailv2&&id=E14DBA5A1D6082E2…7226085359&thid=OIP.M7cf9f637bad11855cde346ba3f8cddb1H0&PC=U316&ajaxhist=0' was loaded over HTTPS, but requested an insecure resource 'http://3.bp.blogspot.com/-WHW5J1uTTCY/UERgSSUImII/AAAAAAAAAMk/JrIBdXHajj0/s1600/Cat+Pictures+8.jpg'. This request has been blocked; the content must be served over HTTPS. The problem is that bing does not handle HTTPS correctly. If you navigate to bing.com, then you'll end up at www.bing.com w/o the secure connection. Here it does work as you mentioned. If you navigate to https://www.bing.com, then the same problem happens as the mixed content is not handled correctly for Chrome's security policy. |
||
►
Sign in to add a comment |
||
Comment 1 by mariakho...@chromium.org
, May 5 2016Owner: mariakho...@chromium.org
Status: Assigned (was: Unconfirmed)