Open
Bug 162369
Opened 21 years ago
Updated 7 months ago
scrolling to named anchor doesn't consider areas covered by fixed positioned elements
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: asa, Unassigned)
References
()
Details
(Whiteboard: [IGNORE COMMENTS 5 THROUGH 8] [webcompat])
Attachments
(1 obsolete file)
a named anchor is not scrolled to the correct position. In my weblog I have a fixed position div that acts as a banner at the top of the page. I also have a primary content div that scrolls behind the fixed position banner div. I set top: 6em; on the primary content div so that the top blog entry displays lower in the viewport than the fixed position banner div. When I click on a link to a named anchor the page scrolls the anchor to the top of the viewport which is behind the fixed position banner div. It should scroll the anchor to the "top" which I've specified as 6em lower than the top of the viewport. Hixie said this might be a Mozilla bug. It might also be that I don't know what I'm doing or that my expectations are broken and not Mozilla's layout. There is no good way to test this on winIE since winIE doesn't do fixed position. Opera and MacIE display the same behavior as Mozilla. Tested with latest trunk and latest 1.1 branch builds on windows, linux and mac.
Reporter | ||
Updated•21 years ago
|
QA Contact: petersen → ian
Comment 1•21 years ago
|
||
Any possible way of fixing this seems like it would be pretty ugly. It seems that what you really want is to have the scrollbar be on something that is the size of the visible area of the body. However, that's hard without frames. (Yet again, back to the question of why the HTML folks waited until 2002 to come up with a good frames design rather than doing better frames in 1997...)
![]() |
||
Comment 2•21 years ago
|
||
*** Bug 171404 has been marked as a duplicate of this bug. ***
![]() |
||
Comment 3•21 years ago
|
||
*** Bug 171036 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
OS: Windows 2000 → All
![]() |
||
Comment 4•20 years ago
|
||
*** Bug 206677 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Summary: named anchor not scrolling to correct position → named anchor scrolls to wrong position (involves fixed positioning)
Comment 5•20 years ago
|
||
This example shows that selecting a named anchor does not scroll to the right position. All contents between <a> and </a> should be seen.
Comment hidden (off-topic) |
Comment 8•19 years ago
|
||
(i don't post comments/bugs often, but i like to get them right and not post duplicates.) this looked like the closest match and the testcase in comment 5 does not involve fixed positioning, so i took the summary's parentheses to mean optional.
Updated•19 years ago
|
Whiteboard: [IGNORE COMMENTS 5 THROUGH 8]
Updated•19 years ago
|
Attachment #136366 -
Attachment description: Test case → test case for some other bug
Attachment #136366 -
Attachment is obsolete: true
Comment 9•18 years ago
|
||
Is there a work-around to allow the use of the spacebar or page down for scrolling on pages with fixed position elements?
Updated•18 years ago
|
Summary: named anchor scrolls to wrong position (involves fixed positioning) → scrolling to named anchor doesn't consider areas covered by fixed positioned elements
Updated•14 years ago
|
QA Contact: ian → layout
![]() |
||
Comment 12•7 years ago
|
||
An example of this issue. https://webcompat.com/issues/3516
See Also: → https://webcompat.com/issues/3516
Whiteboard: [IGNORE COMMENTS 5 THROUGH 8] → [IGNORE COMMENTS 5 THROUGH 8] [webcompat]
Comment 13•4 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 14•4 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•4 years ago
|
Webcompat Priority: ? → ---
Updated•2 years ago
|
Assignee: dbaron → nobody
Updated•8 months ago
|
Severity: normal → S3
Comment 17•7 months ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 7 duplicates.
:dholbert, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dholbert)
Comment 18•7 months ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(dholbert)
You need to log in
before you can comment on or make changes to this bug.
Description
•