Google's Image Search Page Up Problem?

[Ant]

Hello!

If I scroll down enough and then press page up key to go up a screen,
then it goes back to the beginning instead. It acts as if I was pressing
the home key. I noticed in both two Windows' SeaMonkey v2.15.1 and
Debian's IceWeasel (aka Firefox) v18.0.1 web browsers. Is this a bug in
Mozilla's Geck web browser engine or Gooogle?

Thank you in advance. :)
--
"Individually, ants are stupid. Together, they're brilliant." --unknown
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[VanguardLH]

"Ant" wrote:

> If I scroll down enough and then press page up key to go up a screen,
> then it goes back to the beginning instead. It acts as if I was pressing
> the home key. I noticed in both two Windows' SeaMonkey v2.15.1 and
> Debian's IceWeasel (aka Firefox) v18.0.1 web browsers. Is this a bug in
> Mozilla's Geck web browser engine or Gooogle?

Firefox 18.0.1
Windows XP Pro SP-3
(don't have a *NIX distro under which to test)

The default number of hits per page is only 10. Not much scrolling
involved there. I upped the number to 100 (after having to first
disable their Instant search option, save, and then could change the
number of hits per page). You never mentioned HOW you were scrolling
around. I dragged the scrollbar, rolled the mouse wheel, middle-clicked
in the page which activates scrolling and moved the mouse up and down to
scroll, use the up/down arrow keys, and the page up/down keys. When I
had scrolled around quite a bit, I hit the page up key. I only moved
one page up. There was no bouncing back to the home page.

You sure you didn't install something in the web browser that results in
refreshing the web page or clearing the temp file cache?

Since the page up and home keys are right next to each other (on a
standard 101 keyboard), you sure you don't have some gunk in the
keyboard or broken keys (making them over sensitive, like they don't
spring all the way back up so just a touch makes contact)? Tried a
different keyboard? Tried opening a text or other document that is long
and tried the same scrolling procedure to ensure it doesn't happen in
apps other than your web browsers?

[Jim Taylor]

Ant wrote:
> Hello!
>
> If I scroll down enough and then press page up key to go up a screen,
> then it goes back to the beginning instead. It acts as if I was
> pressing the home key. I noticed in both two Windows' SeaMonkey
> v2.15.1 and Debian's IceWeasel (aka Firefox) v18.0.1 web browsers. Is
> this a bug in Mozilla's Geck web browser engine or Gooogle?
>
> Thank you in advance. :)

Internet Explorer 9 on Windows 7 acts the same way so I would assume
it's the way Google wrote the page.

--
Jim

[Ray_Net]

I have the same with IE9 on Windows7 and also with my SM
User agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120909
Firefox/15.0.1 SeaMonkey/2.12.1

[Ant]

> The default number of hits per page is only 10. Not much scrolling
> involved there. I upped the number to 100 (after having to first
> disable their Instant search option, save, and then could change the
> number of hits per page). You never mentioned HOW you were scrolling
> around. I dragged the scrollbar, rolled the mouse wheel, middle-clicked
> in the page which activates scrolling and moved the mouse up and down to
> scroll, use the up/down arrow keys, and the page up/down keys. When I
> had scrolled around quite a bit, I hit the page up key. I only moved
> one page up. There was no bouncing back to the home page.
>
> You sure you didn't install something in the web browser that results in
> refreshing the web page or clearing the temp file cache?
>
> Since the page up and home keys are right next to each other (on a
> standard 101 keyboard), you sure you don't have some gunk in the
> keyboard or broken keys (making them over sensitive, like they don't
> spring all the way back up so just a touch makes contact)? Tried a
> different keyboard? Tried opening a text or other document that is long
> and tried the same scrolling procedure to ensure it doesn't happen in
> apps other than your web browsers?

I can reproduce it on multiple computers, IBM PC keyboards, and latest
Mozilla's web browsers. It doesn't happen anywhere else.
--
"An ant on the move does more than a dozing ox." --Mexican Proverb

[Ant]

On 1/31/2013 2:15 PM PT, Ray_Net typed:

Thanks all. Weird glitch!
--
"... Here's intelligent things, and it seems they want us for food.
First, they'll smash us up -- ships, machines, guns, cities, all the
order and organisation. All that will go. If we were the size of ants we
might pull through. But we're not. It's all too bulky to stop. That's
the first certainty." Eh? ..." --H.G. Wells' The War of the Worlds

[Ant]

http://productforums.google.com/forum/#!category-topic/websearch/google-images/7es2cHaHF8A
shows another user with the same problem. Google doesn't think so. :/
--
"What is it going to be like in eternity with God? Frankly, the capacity
of our brains cannot handle the wonder and greatness of heaven. It would
be like trying to describe the Internet to an ant." --Rick Warren's
book, The Purpose Driven Life

[Paul B. Gallagher]

Ant wrote:

> Hello!
>
> If I scroll down enough and then press page up key to go up a screen,
> then it goes back to the beginning instead. It acts as if I was pressing
> the home key. I noticed in both two Windows' SeaMonkey v2.15.1 and
> Debian's IceWeasel (aka Firefox) v18.0.1 web browsers. Is this a bug in
> Mozilla's Geck web browser engine or Gooogle?
>
> Thank you in advance. :)

I've seen this on lots of pages IF I use some other mechanism (scroll
bar, mouse wheel) to scroll. It acts as if the cursor hasn't moved, so
when I do PgUp or PgDn it calculates from the last cursor position (off
screen), not from the current view.

Not that there is a cursor, but you'll see the analogy if you try it in
MS Word or some other application. Put the cursor on page 2, scroll down
with the mouse wheel, and hit PgUp orPgDn. It takes you to page 1 or 3
as the case may be even if your current display is page 8.

This doesn't happen if I've used PgUp or PgDn to scroll.

--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

[eisneun]

"Ant" wrote in message news:w4WdndA-y9c6H5fM...@mozilla.org...

Hello!

If I scroll down enough and then press page up key to go up a screen,
then it goes back to the beginning instead. It acts as if I was pressing
the home key. I noticed in both two Windows' SeaMonkey v2.15.1 and
Debian's IceWeasel (aka Firefox) v18.0.1 web browsers. Is this a bug in
Mozilla's Geck web browser engine or Gooogle?

Thank you in advance. :)

a workaround, if you can change your keyboard habits:

space bar = one page down
shift + space bar = one page up

How can ace be one and eleven? Huh?
What kind of god would allow that?

[Ray_Net]

Ant wrote, On 01/02/2013 06:53:
> http://productforums.google.com/forum/#!category-topic/websearch/google-images/7es2cHaHF8A
> shows another user with the same problem. Google doesn't think so. :/

Perhaps they don't experience the problem, because they do no use IE nor
SM, they just use their browser Chrome.

They do exactly as microsoft, creating BAD pages ....and the microsoft
browser IE correct the problem before displaying the page.

So microsoft and google both says: You are dumb ... there is no problem
- all is perfect !

Can someone here test the bug with the latest version of Chrome ?

[Ray_Net]

I have tested what you said - i only use PgDown and PgUp .....
PgDown = Down one page
PfUp= Home

[Swifty]

On 01/02/2013 07:38, Paul B. Gallagher wrote:
> I've seen this on lots of pages IF I use some other mechanism (scroll
> bar, mouse wheel) to scroll. It acts as if the cursor hasn't moved, so
> when I do PgUp or PgDn it calculates from the last cursor position (off
> screen), not from the current view.

This seems to be the behavious of the majority of application from my
perspective (perhaps I have a penchant for "broken" apps). I was going
to mention this, now I find myself agreeing with it. That makes me an
agreeable fellow, presumably.

There is definitely a different location kept for PgUp/PgDown and
scolling with the slider/mousewheel in most of my applications.

I suppose you could turn it to your advantage (I often do). When I've
reached a point of interest, I click something in the page that won't
have any effect. This forms a sort of "bookmark". I can now scroll
around to my hearts content WITH THE MOUSE, then go back to my
"bookmark" with a PgUp/PgDown.

[Ant]

On 1/31/2013 9:53 PM PT, Ant typed:

> http://productforums.google.com/forum/#!category-topic/websearch/google-images/7es2cHaHF8A
> shows another user with the same problem. Google doesn't think so. :/

Finally, Google reproduced it! :D
--
"In an ant colony, dew is a flood." --Afghan

[Ray_Net]

Ant wrote, On 02/02/2013 07:46:
> On 1/31/2013 9:53 PM PT, Ant typed:
>
>> http://productforums.google.com/forum/#!category-topic/websearch/google-images/7es2cHaHF8A
>>
>> shows another user with the same problem. Google doesn't think so. :/
>
> Finally, Google reproduced it! :D

I this post why you said that Google reproduced it ?

----------------------

Jessica S.
Autres actions sur les messages
00:22 (il y a 22 heures)

Hi Ant,
This is indeed a technical issue. We'll keep you posted when we have an
update.
Thanks!
Jess
---------------------------

Is Jessica a Google Technical people ?