Closed
Bug 278213
Opened 20 years ago
Closed 16 years ago
Back button does not restore position after jump within current page
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
INVALID
People
(Reporter: relf, Unassigned)
References
()
Details
Linux build 2005011014 To reproduce: 1. Open provided URL 2. Scroll down to the section 4.1 3. Click on ``[1]'' link (near the section number) It will position within current page. 4. Click Back button and it will take you to the top of the page instead of Section 4.1
| Reporter | ||
Updated•20 years ago
|
OS: Linux → All
Hardware: PC → All
Comment 2•20 years ago
|
||
I noticed that there are two 4.1 that I can click on, the first one at the very top and the 2nd one in the middle. Are you referring to the 2nd one??
Comment 3•19 years ago
|
||
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/
| Reporter | ||
Comment 4•19 years ago
|
||
confirming per comment 1
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•19 years ago
|
||
I can confirm the reported bug. Very annoying!
This bug seems to be at least on Mozilla 1.7.1.2 and Firefox 1.5.0.1. Tried using Internet Explorer 6 & Opera 8.5 with the same page that had the problem and they worked correctly. Very annoying bug! Using Windows Xp, same bug also on linux.
Comment 7•18 years ago
|
||
I'm just a schmuck user, not a developer, but I can confirm this in FF 2.0, unless I'm missing some intentional behavior. I'm noticing that it happens under two conditions: 1) accessibility.browsewithcaret is set to TRUE (or "Always use the cursor keys to navigate within pages" is checked; which also sets the former flag, and 2) You sit on the target page for a while before clicking Back. Do it right away, it works as expected. Wait a minute or so, and I can repro it pretty consistently. Set the flag to FALSE (either in about:config or through clearing the aforementioned checkbox) and the issue goes away. This was confirmed on both Windows XP and Windows 2000 machines.
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
Comment 8•16 years ago
|
||
original URL is dead. still fails for archived version http://web.archive.org/web/20041225235414/http://www.pixel-apes.com/translit/conversiontables
Severity: normal → minor
Comment 9•16 years ago
|
||
This page has a JS click handler which scrolls the page to the new location _before_ we actually react to the click. So by the time we're doing session history stuff, the scroll position is the new one, and that's what we save. This is at least for the web.archive.org page in question; comment 7 sounds like a totally different issue deserving a separate bug with a testcase, since I can reproduce the bug on the page here just fine without browse-with-caret. Not an issue in our code; the page should stop messing with navigation...
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•