>Google has long been under fire from photographers and publishers who felt that image search allowed people to steal their pictures, and the removal of the view image button is one of many changes being made in response. A deal to show copyright information and improve attribution of Getty photos was announced last week and included these changes.
Using the context menu to "Open Image in New Tab" essentially does the same thing so the functionality is still there.
> using the context menu to “Open Image in New tab” essentially dos the same thing so the functionality is still there.
No, actually “view image” loaded the source image at source resolution while viewing the image loaded into the DOM would show you the re-encoded, lower resolution, smaller Google thumbnail version.
Edit: actually it seems that Google has simultaneously deployed an update that makes the actual source image open so that might actually work.
What I'm seeing on the current site is that the large preview seen on clicking a thumbnail is the original image, loaded from the original server and scaled in CSS.
Nothing's really changed in terms of capability; the UI is just a bit more awkward.
Only images you click on (so that the larger preview pops up, with the Visit button and which used to have the View image button) load the original images, rescaled with CSS. The grid of smaller images consists of thumbnails.
Are you sure you're actually clicking the images first, so they're brought up in the image viewer box with the other options available, and then right-clicking -> View Image/Open Image/whatever?
If you are, then that's very strange, and I have no idea why that's happening for you and not for anybody else. What browser and OS are you using?
> It is too slow to load many such large images automatically.
The images don't all load automatically, though; an image only begins to load when you click on it individually, opening it within the viewer, on a Google Images results page.
Here[0] is a screenshot example. Clicking on 'Open image in new tab' (or 'View Image' in Firefox) will open the image[1] directly, and inspecting the page's source will reveal it is simply an <img> element with the URL as the src value. The size ought to make no difference; I tried up to 10 MP.
It may take a second to load, but that's how Google Images works: once an image is open in the viewer, it is quite literally just embedding the unadulterated source image within the page. It has been this way since at least 2010.
(Unless, of course, there is behaviour unique to Safari or OS X: of that I have no idea.)
In this comment and especially in https://news.ycombinator.com/item?id=16323396, you've violated the site rules badly. You've also posted a bunch of unsubstantive comments and ignored our request to stop doing this.
We ban accounts that behave this way, so would you please (re-)read https://news.ycombinator.com/newsguidelines.html and comment only in the spirit of this site from now on? That means being scrupulously respectful of others, and generally not posting unless you have something substantive to say and can do so thoughtfully.
I am not sure, but read somewhere on HN Google related article comments that what Google does is first load all image search page with own encoded compressed thumbnails, enlarged by css, and then async fetches the real images, replaces the thumbnails, and scales down by css to show as same size of thumnail.
>Google has long been under fire from photographers and publishers who felt that image search allowed people to steal their pictures, and the removal of the view image button is one of many changes being made in response. A deal to show copyright information and improve attribution of Getty photos was announced last week and included these changes.
Using the context menu to "Open Image in New Tab" essentially does the same thing so the functionality is still there.