264783 - Page-down, page-up, end, home do not work as expected

Status: RESOLVED EXPIRED

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Remigius bunia]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.3) Gecko/20040910

On more complex pages (but without frames!) the following keys do not behave
properly: page down, page up, end, home. It is especially impossible to get back
to the top of the page without using the mouse (or holding arrow-up for a long
time).

Reproducible: Always
Steps to Reproduce:
1. Open "www.faz.net"
2. Press <page down>


Actual Results:  
Page flickers and doesn't scroll down.

Expected Results:  
It should have scrolled down.

Comment 1

[Hermann Schwab]

wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910

german windows98, german keyboard, tested separate keys and those from the
numberblock, all working.

Reporter, do you have extensions installed?

Comment 2

[Gérard Talbot]

WORSKFORME Mozilla 1.8a5 build 2004101605 under XP Pro SP2 here.

Comment 3

[Remigius bunia]

No, I don't use any extensions. Please try www.faz.net and <page down>; I
suppose the advertisement banners contribute to the strange behavior. The
error does not occur with Firefox 0.9.3 (engine: Mozilla/5.0 (Windows; U;
Windows NT 5.1; de-DE; rv:1.7) Gecko/20040803 Firefox/0.9.3).

And another thing: I just remarked that Mozilla hasn't finished loading the
page, i.e. it says 'download completed' but still show the progress bar.
Maybe I cannot navigate with the keys because Mozilla thinks the page is
still being loaded? Firefox behaves correctly also with respect to the
progress bar.
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.3)
Gecko/20040910
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.3)
Gecko/20040910
> 
> On more complex pages (but without frames!) the following keys do not behave
> properly: page down, page up, end, home. It is especially impossible to get back
> to the top of the page without using the mouse (or holding arrow-up for a long
> time).
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Open "www.faz.net"
> 2. Press <page down>
> 
> 
> Actual Results:  
> Page flickers and doesn't scroll down.
> 
> Expected Results:  
> It should have scrolled down.

Comment 4

[Gérard Talbot]

> Please try www.faz.net and <page down>;
We did: it works as expected.

Comment 5

[Hermann Schwab]

(In reply to comment #4)
> > Please try www.faz.net and <page down>;
> We did: it works as expected.

The reporter is using a Mozilla 1.7.3, not 1.8a5.
Good to know that the bug is not in trunk, but it maybe in 1.7.3, when the
german language pack is installed.


reporter, can you retry with language set to english?

from comment #0:
On more complex pages (but without frames!) the following keys do not behave
properly: page down, page up, end, home.

Does that mean, these keys are working on other pages? 
They are only failing on faz.net?

If they are failing always, maybe there is a hardware problem.
Do you use a normal german keyboard, or a cordless version, or a notebook?
Do you use a german Windows XP?

can you do a keyboard test, using the following URL:
https://bugzilla.mozilla.org/attachment.cgi?id=55849&action=view

pagedown gives:
1) keydown charCode=0 keyCode=34 character=|
2) keypress charCode=0 keyCode=34 character=|
3) keyup charCode=0 keyCode=34 character=|

Comment 6

[Remigius bunia]

Yes, it's on faz.net. But I have another idea. It's on all pages where there's a
Flash object in them. I have no Flash plug-in.

Comment 7

[Hermann Schwab]

(In reply to comment #6)
> Yes, it's on faz.net. But I have another idea. It's on all pages where there's a
> Flash object in them. I have no Flash plug-in.

I don´t think that flash is the culprit. I just tested using 1.7.3, was looking
for flash, and only found the small american flag on the top. Went to this page
about American Elections, and shortly after a dialog popped up telling me I got
a popup, and if I want to allow it, or block all popups. I canceled the dialog,
and the popup went to the tray. I couldn´t use the PageUp and PageDown keys,
until I opened the popup, and saw, they were working there. So the popup in the
tray had got keyboard focus.
Workaround: click somewhere on the page, so it gets focus again.

Now using todays trunk nightly, I got a big fat popup, sent it to the tray, and
some ten seconds later, I saw 'loading adserver.de' in the status bar, and the
PageUp/pagedown keys were blocked again. The popup was a questionnaire for an
insurance company, containing a form with lots of inputs and selects, and some JS.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.