Closed Bug 945422 Opened 11 years ago Closed 6 years ago

Absolute positioned element bound by position static parent

Categories

(Core :: General, defect)

25 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: curtdulmage, Unassigned, NeedInfo)

Details

Attachments

(1 file)

Attached image ff-bug.jpg
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 Steps to reproduce: The body element is set to "relative". I have an absolutely positioned element within a position static container. For some reason, the position absolute element is bound by the position static element... which should not be the case. This only happens in Firefox (and every version of FF I've tested, both Windows and Mac). In every other browser it works as expected, even IE8. Here is the staging site: http://chickenfarmers.armystage.com/ The absolutely positioned element is: ul#secondary-navigation Actual results: Absolutely positioned element is being positioned within its static parent... not the position relative body. Expected results: Absolutely positioned element should be positioned relative to the body element.
I see nothing resembling your Firefox screenshot in either a Firefox nightly or Firefox 25. Which Firefox version are you using? Is this a problem in safe mode?
Flags: needinfo?(curtdulmage)
My main dev browser is Firefox 25.0.1 on OS X 10.9 I have tested this on a few different versions of FF on Windows XP, 7, and 8.1 ... however, I just tried FF 4.0 on Windows 7 using Browser Stack and the element was rendered properly! My free trial expired immediately after :( so I couldn't continue testing. Also, I just relaunched FF in safe mode and still, the same issue where the element is not positioned properly. I hope this information is sufficient. If there is anything more I can provide please let me know. Thanks,
Is this still an Issue? On my site this is WFM against Firefox 24 ESR & Trunk on Windows 7 with HWA on/off.

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: