Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-09-16 01:48:22 +01:00
Code Issues Projects Releases Packages Wiki Activity

layout: Ensure IFC for abspos with inline-level original display (#39041)

Browse source 
Absolutely positioned elements get blockified, but their static position
still depends on the original display. Therefore, if we encounter an
abspos with an inline-level original display, we will now ensure that
it's handled in an inline formatting context. This way its static
position will correctly take into account things like `text-align`.

Testing: Several WPT tests are now passing.
Fixes: #39017

Signed-off-by: Oriol Brufau <obrufau@igalia.com>
This commit is contained in:
Oriol Brufau 2025-09-02 05:43:55 +02:00 • committed by GitHub
parent 665ee150a6
commit 9264ef1a95
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
17 changed files with 42 additions and 44 deletions
Download patch file Download diff file Expand all files Collapse all files

2
tests/wpt/meta/css/css-position/position-absolute-dynamic-static-position-floats-001.html.ini vendored
View file

@ -1,2 +0,0 @@
[position-absolute-dynamic-static-position-floats-001.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/position-absolute-dynamic-static-position-floats-002.html.ini vendored
View file

@ -1,2 +0,0 @@
[position-absolute-dynamic-static-position-floats-002.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/position-absolute-dynamic-static-position-floats-003.html.ini vendored
View file

@ -1,2 +0,0 @@
[position-absolute-dynamic-static-position-floats-003.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/position-absolute-dynamic-static-position-floats-004.html.ini vendored
View file

@ -1,2 +0,0 @@
[position-absolute-dynamic-static-position-floats-004.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-001.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-001.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-002.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-002.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-003.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-003.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-005.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-005.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-006.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-006.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-008.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-008.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-009.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-009.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-010.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-010.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-011.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-011.html]
expected: FAIL

2
tests/wpt/meta/css/css-position/static-position/inline-level-absolute-in-block-level-context-012.html.ini vendored
View file

@ -1,2 +0,0 @@
[inline-level-absolute-in-block-level-context-012.html]
expected: FAIL