Broken image when opening in background tab via middle button/ctrl+left click
-
I've searched the forum and it seems no one has reported this one yet, not sure if it's just me? Using middle button to open an image in a new background tab is very important in my daily workflow but whenever I use the middle mouse button or ctrl+left click on any hyper-link that ends with .jpg/.png/.gif etc, the new background tab will only show a Chrome broken image icon. Everything goes back to normal with the image shown properly if I refresh the tab or if/after the linked image is already in my cache. If I have opened the image link with any option from the right click context menu, including "Open link in background tab", no problem will occurs. I've tried clearing my browsing data/private window and the problem persists. Any idea? P.S Can we get closing the last tab closes the window back?
-
Thanks for the quick reply. I'm on 1.0.390.3 64bit on Windows 8.1x64.
Yes the problem does not always happen with every image, after some testing, seems like it can be isolated to the specific domain that host the image, links below are examples that's giving me the problem
https://imgs.moe/my/study/geography/src/1454391637899.jpg
https://imgs.moe/my/study/geography/src/1438604443383.jpg
http://myth.nagatoyuki.org/src/1455513208214.jpg
http://myth.nagatoyuki.org/src/1455517714235.jpg
http://gzone-anime.info/UnitedSites/books/src/1403881992942.jpg
http://ningen.dreamhosters.com/moe/src/1454326937036.jpgBut after some more testing, some pics on imgur are giving me problem but some are not. Very curious.
Also after an given image has successfully loaded, that link/image will never have any problem again. If I clear privacy data (image cache) then it comes back.
-
Thanks a lot, hope this get fixed soon.
However not sure if this problem is limited to large images, the following link fails with a 9kb 300*169 image
https://imgs.moe/my/study/geography/src/1424793132133.jpg
I've also opened 30+mb super high res images without a problem.
-
The problem seems to be resolved in the latest snapshot. Good job!
-