Off by one pixel error using Page Up/Down buttons




16 years ago
13 years ago


(Reporter: peter_c60, Assigned: saari)



Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030503 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030503 Mozilla Firebird/0.6

The Page Down button scrolls the screen down one more pixel than the Page Up
button scrolls it up.

Reproducible: Always

Steps to Reproduce:
1. Go to a web page bigger than 2 pages of text and enter in the address bar
2. Press the Page Down button. If you are using smooth scrolling, wait for the
screen to stop scrolling. The bug is irreproducible if you do not wait.
3. Press the Page Up button.
4. Go to javascript:alert(document.body.scrollTop) again.

Actual Results:  
The value will be 1 pixel greater than it was before.

Expected Results:  
The value should be the same as it was before.

I am using a 1024x768 screen, if it matters. I am also using an old version of
Firebird, someone should confirm with a recent build. I am using a custom GTK 2
and Xft build of Firebird. This bug is not reproducible if you use the area
above/below the scroll box to scroll up or down a page; neither is it
reproducible if you use the arrow keys or the up/down buttons on the scroll bar.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.