Closed
Bug 256565
Opened 20 years ago
Closed 20 years ago
Browser jumps back to top of page when link is clicked or onmouseover event; scroll bars often incorrectly sized
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 256436
People
(Reporter: avbohemen, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040822 Firefox/0.9 (BlueFyre)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040822 Firefox/0.9 (BlueFyre)
See url, then go over one of the "powered by" links in the bottom of the page.
It should display a layer with info on the sponsor of that site. Instead,
firefox jumps back to the top of the page, making it impossible to click the link.
Another example: Do a search in Bugzilla that results in a lot of hits (I tried
"scrollbar" before entering this bug). Scroll down to the bottom and try to
click a bug. Result: the page jumps back a bit (this happens when the
mousebutton is pressed, not when it is released), the specified bug is not
loaded. In addition, the size of the scrollbars is suddenly totally wrong (too
small). You can't scroll to the bottom of the page anymore by dragging the
scrollbar. Scrolling the mousewheel or pressing the down arrow works though.
Another example: also in bugzilla, in the enter a bug page, try to change the
"reproducability" dropdown box. Again the page jumps.
Also: entering text in input boxes doesn't display scrollbars correctly or at
all. I'm having it now in the details-box of bugzilla.
Reproducible: Always
Steps to Reproduce:
1. Do one of the examples mentioned above.
2.
3.
Actual Results:
Page jumps up, and/or scrollbars resize incorrectly.
Some links are impossible to click.
Expected Results:
Don't jump the page.
I also tried a aviary branch build, this works normal. It seems specific to the
trunk / 1.8a3 builds.
Just guessing: Related to bug 256282 and/or Bug 252920 etc.?
Reporter | ||
Comment 2•20 years ago
|
||
After some more careful searching, it is a duplicate of bug 256436. This was
resolved by backing out a patch for bug 255584, which is dependent on bug
252920... resolving.
*** This bug has been marked as a duplicate of 256436 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•