When on google, just using firefox, if I'm scrolling through images using the arrow keys, it'll stop scrolling after around 4-5 pictures.
So on occasion I'll google an image and I'll click on the first one and use the arrow keys to continue going through the rest. However, in the past week or so, I've noticed that when I do that, the arrow keys won't work after the first couples images. It'll just stay on the image I'm currently on and won't go to the next image.
I haven't changed any settings, haven't added any new extensions, and this happens on both Windows 10 and Ubuntu, so it seems to be a browser issue rather than an OS input issue. What might be happening and how can I fix this?
所有回覆 (4)
Example of the google image search your using that is causing the error?
Here is a video of it. https://youtu.be/eVcVeHa4XpI
You know, I just noticed that. Normally you can show the first image on the black box, and then press the right arrow key to view the next image in larger size, and repeat until your hand gets tired. Now, it seems that quite frequently, the arrow key stops working -- you can't go forward or back.
When the arrow stops working, it is when a link around the large image is selected. Google's scripts related to that link may be capturing and discarding the arrow keypress for some reason. It seems most likely to occur when the quality goes from low to high for a particular image, and it's an image stored by Google instead of displayed from the original source site, but it could be a coincidence.
As a temporary workaround to kick start the arrows, you can press the Tab key to move the focus from the link where it's stuck to the next link, or click anywhere on the black rectangle, or click on another image. I can't tell why this is necessary now; it is pretty annoying.
It seems to be related to the case where a low-res version is shown initially, and you see a "loading bar" animation along the bottom of the image. (Sample screenshot attached.) As soon as the high-res version is displayed, the arrow keys stop working. I don't know why that affects Firefox but not other browsers.
