Bug 67491

Summary: Incorrect horizontal auto position for abs pos elements at the start of a block
Product: WebKit Reporter: Boris Zbarsky <bzbarsky>
Component: Layout and RenderingAssignee: alan <zalan>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, hyatt, karlcow, phiw2, simon.fraser, zalan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Another testcase with float showing the inconsistency depending on whether the abs pos thing is first in the block none

Boris Zbarsky
Reported 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.
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
View All Add attachment proposed patch, testcase, etc.
Boris Zbarsky
Comment 1 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
Ahmad Saleem
Comment 2 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!
alan
Comment 3 2023-03-28 08:03:36 PDT
Firefox produces correct rendering. This is going to progress in WebKit when bug 254394 is landed.
alan
Comment 4 2023-03-29 15:01:58 PDT
This is fixed now (262277@main) (IFC progression).
Note You need to log in before you can comment on or make changes to this bug.