Sep 28, 2018 - Adds a context menu item to open images in a new tab - MethodGrab/firefox-open-image-in-new-tab. I am a convert from Chrome. Opening images in new tabs is one of my favorite Chrome features. Is it possible to do this with Firefox?
Where Is My Firefox Browser
View Image is a browser extension for and that adds a 'view image' button to Google Images so that users can click on it to display the image directly in the browser.from its image search engine Google Images recently after the company came to an agreement with Getty Images.The button loads the image that is displayed directly. This gives users options to look at it more closely and to download it to the local device that they use.While it is still possible to to do after the removal of the button on Google Images - users can still right-click on the image and select 'open image in new tab' or a similar option - view image made the whole process easier and many Internet users probably don't know that they can open the image through the context menu.We suggest that you use a. You can view images directly on Startpage and images do get opened through a proxy so that your IP address is not revealed to the site hosting the image. View Image extensionView Image is a new browser extension for Firefox and Chrome that adds the button to Google Images again.The extension should work in compatible browsers such as Opera or Vivaldi as well, and the functionality of it is identical.The extension does require access to your browsing data on all Google sites and the code is available. Closing WordsGoogle users who used 'view images' in the past regularly to load images in a standalone tab may use the View Image browser extension to restore the functionality.
Most users don't need it probably though as it is still possible to right-click on images to load them individually.Now You: Which site do you use for image searches?
8 years ago(In reply to Gavin Sharp (use for email) from ) Loading the image in the current tab doesn't cause 'dataloss' in any meaningful sense of the word, unless you're referring to the edge case of un-cached responses to POST submissions.We also don't restore plugin and web app states (e.g. I'm only mentioning this for completeness. What I think is more relevant is that replacing the page seems inconvenient; my experience is that I usually go back manually after using View Image. This bug was originally about adding a menu item, so morphing it to cover a change in behavior of the existing menu item doesn't seem ideal.I'm pretty sure we don't want to fix this bug as-filed, as this would clutter up the context menu.
I think we just need some sensible default behavior here. 8 years agoIt looks to me like my context menus have a lot of items that aren't as context-sensitive as they could be - in particular, many items appear regardless of where the click is, so the menu is longer on a link or image than on a blank part of the page. Better segregation might make it less of a problem to have similar items like 'open image in this tab' and 'open image in new tab'There could also be a submenu at the top named something like 'menu items open new tabs', with submenu items to change that to this tab or new window. That's basically adding a preference, and giving every menu an item which indicates the state of that preference and allows you to change it.Since the menus persist after the button is released, there could be another context menu for the context menu items, but that might be even weirder than modifier keys on context menu items. Since modifier keys are supported, the menu item text should change when the modifiers are pressed or released.The simplest thing might be to add to the menu item some indication that modifier keys are supported - maybe even a tooltip?