341254 - relative link causing a portion of the page to disappear

Status: RESOLVED DUPLICATE of bug 325942

(Core :: Layout, defect)

Description

[Will Holcomb]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

Following a relative link (#something) causes the page above the target to disappear.

Reproducible: Always

Steps to Reproduce:
1. Click on one of the relative navigation links at the top of the page.
2. Scroll up.
3. Note that the top of the page is now gone.
4. Go back a page.
5. Note that the top of the page is still gone.
Actual Results:  
All content in the page above the target of the link is gone.

Expected Results:  
Clicking a relative link shouldn't cause a portion of the page to disappear. If for some reason it should, hitting and returning to the base url should make them come back.

The contents of the center div are within an overflow: hidden div with a large bottom padding and large negative bottom margin to allow for same height columns.

Firefox XP shows the same behavior.

There is a similar behavior in IE (it leaves the top header and navbar, but crops the content div).

Safari and Opera perform as expected.

Comment 1

[Ria Klaassen (not reading all bugmail)]

I see it also in old Firefox 1.0.7, Windows XP.

Comment 2

[Ralf Vitasek]

this is not a bug.

the reason for this behaviour is the main content residing in the div with id overflowcrop which has the following style set in position.css:

#overflowcrop, #maincrop { overflow: hidden; }

remvoe that style and your "bug" will be gone (in case its your website otherwise if it disturbs you, tell the webmaster of that site)

Comment 3

[Mats Palmgren (inactive)]

(In reply to comment #2)
> this is not a bug.

Uhm, yes it is actually. I tested with one of my patches for bug 325942
and the scrolling at the URL works fine without clipping.

Comment 4

[Mats Palmgren (inactive)]

*** This bug has been marked as a duplicate of 325942 ***

Comment 5

[devinivy]

I would love to see this bug fixed, as it can lead to nasty phishing ploys without JavaScript!