Closed
Bug 264678
Opened 20 years ago
Closed 20 years ago
Anchors not properly scrolled to on http://www.imdb.com
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: eric, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 When clicking one of the links on the top right of http://www.imdb.com (any link in the Movie and TV News section), Firefox does not properly scroll to the selected anchor. Reproducible: Always Steps to Reproduce: 1. Go to http://www.imdb.com 2. Click on any link in the "Movie and TV News" section Actual Results: Firefox scrolls about 5-6 lines too low on the next page. We can see that it initially does go to the proper anchor, but scrolls down a bit further about half a second afterwards. Expected Results: Firefox, as in Seamonkey, IE, Opera, etc., should scroll and stick to the selected anchor.
| Reporter | ||
Comment 1•20 years ago
|
||
Requesting blocking 1.0. I think there's probably a very easy workaround to this problem (which has been around for ages now), and it'd be nice to get it fixed in time for release.
Flags: blocking-aviary1.0?
Comment 2•20 years ago
|
||
Odd, it works perfectly for me, with the exact same build.
Comment 3•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 ->WFM clear your cache and try again
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 4•20 years ago
|
||
Don't request blocking on unconfirmed bugs, they're not gonna get plussed If no one else sees the bug.
Flags: blocking-aviary1.0?
| Reporter | ||
Comment 5•20 years ago
|
||
Tried clearing cache...still see the bug. I've been seeing this for a long time now.
| Reporter | ||
Comment 6•20 years ago
|
||
Hmm....works for me with a new profile now. Damn profile bugs. Not like this is an old one, either.
You need to log in
before you can comment on or make changes to this bug.
Description
•