Bug 67491 - Incorrect horizontal auto position for abs pos elements at the start of a block
Summary: Incorrect horizontal auto position for abs pos elements at the start of a block
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: zalan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 09:47 PDT by Boris Zbarsky
Modified: 2023-03-29 15:01 PDT (History)
6 users (show)

See Also:


Attachments
Another testcase with float showing the inconsistency depending on whether the abs pos thing is first in the block (652 bytes, text/html)
2011-09-02 09:48 PDT, Boris Zbarsky
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Zbarsky 2011-09-02 09:47:00 PDT
See testcases at https://bug682780.bugzilla.mozilla.org/attachment.cgi?id=556570 and https://bug671491.bugzilla.mozilla.org/attachment.cgi?id=545914

The former involves a float; the abs pos element should be to the right of the float.

The latter involves "text-align: center"; the abs pos element should have its left edge centered in the block.

Presto seems to have a similar bug.  Gecko and Trident seem to get this right.
Comment 1 Boris Zbarsky 2011-09-02 09:48:09 PDT
Created attachment 106144 [details]
Another testcase with float showing the inconsistency depending on whether the abs pos thing is first in the block
Comment 2 Ahmad Saleem 2023-03-27 10:13:56 PDT
Attached test case - Chrome Canary 114 & Safari Technology Preview 166 match each other while Firefox Nightly 113 is showing 'expected result'.

While following mentions:

Test Case - https://bug671491.bmoattachments.org/attachment.cgi?id=545914

^ All browsers are matching.

Just wanted to share updated test result. Thanks!
Comment 3 zalan 2023-03-28 08:03:36 PDT
Firefox produces correct rendering. This is going to progress in WebKit when bug 254394 is landed.
Comment 4 zalan 2023-03-29 15:01:58 PDT
This is fixed now (262277@main) (IFC progression).