You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect "i" shortcut to open the images tab in the search. While in the images tab, I expect "a" or "s" to return me to the main search listing. Neither of these are currently true. "i" does nothing, "a" and "s" take me to images, and while in images, "a" and "s" do not return me to the main page.
Perhaps this is related to recent Google search layout changes / changes in the way that the tabs are positioned?
Browsers
Chrome
Other extensions
Yes
Version
0.5.2
Troubleshooting result
I have followed the troubleshooting section
Anything else
No response
The text was updated successfully, but these errors were encountered:
I can't reproduce this, have you followed the troubleshooting guide? please add a screenshot of the browser window opened as part of troubleshooting (in Google Search)
I can't reproduce this, have you followed the troubleshooting guide? please add a screenshot of the browser window opened as part of troubleshooting (in Google Search)
I seem to have a similar issue, my "i" key or any other key that I set to open images doesn't seem to work. All the other tabs seem to work fine (news, videos, maps etc.). I have tried on Chrome, Edge and Brave all seem to have the same issue not being able to launch google images from the search result page.
Related issues
What happened?
I expect "i" shortcut to open the images tab in the search. While in the images tab, I expect "a" or "s" to return me to the main search listing. Neither of these are currently true. "i" does nothing, "a" and "s" take me to images, and while in images, "a" and "s" do not return me to the main page.
Perhaps this is related to recent Google search layout changes / changes in the way that the tabs are positioned?
Browsers
Chrome
Other extensions
Yes
Version
0.5.2
Troubleshooting result
Anything else
No response
The text was updated successfully, but these errors were encountered: