Closed Bug 441267 Opened 16 years ago Closed 13 years ago

Wrong positioning for absolute positioned elements

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: kes-kes, Unassigned)

Details

Attachments

(3 files, 1 obsolete file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; ru; rv:1.9) Gecko/2008052906 Firefox/3.0

see attached file

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Attached image test case
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Eugen, do you have the source of that page or an url somewhere?
Attached file test case (obsolete) —
Attachment #326629 - Attachment is obsolete: true
Attached file test case
Attachment #326271 - Attachment is obsolete: true
Attachment #326271 - Attachment is obsolete: false
Comment on attachment 326630 [details]
test case

type something long in input field near Fetch
Right and bottom for absoluted positioned elements that are replaced doesn't work anymore. That is according to CSS2.1. See bug 423397.
A text input is a replaced element, so that is why the text input is wider now with your testcase.

For the rest, I don't really see a difference compared to FF2 with your testcase.
Same problem, different explanation (check testcase):

FF3 do not calculate position relative to its closest positioned ancestor when an absolute positioned table is contained inside another absolute positioned table (using relative to initial containing block => window)
It seems to me that my comment and test-case is a separate case?

Eugen Konkov's testcase may not be a bug and I believe as Martijn Wargers that this was the same in FF2:

FF3 gives INPUT a width: 151px (fontSize=13px) ( and length: 149 (??)) as default 
(INPUT has no size or width attribute and no width or max-width in style)

Confusion around these issues is very common and may be partly due too:

- Setting width or max-width on containing element is not respected (bug ?)
- Setting width-attribute has no effect (bug?)
- Setting style='width: 40px' limits width
- Setting style='max-width: 40px' limits width more (?) (bug?)
(In reply to Terje Rosenlund from comment #7)
> Same problem, different explanation (check testcase):

Completely differen issue. What you describe is bug 10209 and/or bug 63895. There is a patch on the way in another bug that will fix those issues.

(In reply to Terje Rosenlund from comment #9)
> - Setting width or max-width on containing element is not respected (bug ?)
> - Setting width-attribute has no effect (bug?)
> - Setting style='width: 40px' limits width
> - Setting style='max-width: 40px' limits width more (?) (bug?)

All those cases appear to work correctly and identically in Firefox and other browsers.

I'll resolve this report as Invalid because the input element behaves correctly.
The table issue has its bugs and does not really fit in here (so I don't dupe the report).
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: