Closed Bug 2089428 Opened 14 days ago Closed

[wpt-sync] Sync PR 64457 - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=277228

Categories

(Core :: Web Painting, task, P4)

task

Tracking

()

RESOLVED FIXED
162 Branch
Tracking Status
firefox162 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 64457 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/64457
Details from upstream follow.

Karl Dubost <karlcow@apple.com> wrote:

WebKit export of https://bugs.webkit.org/show_bug.cgi?id=277228

WebKit export from bug: filter on an inline element does not apply to a block-<!---->level descendant

<pre>
filter on an inline element does not apply to a block-level descendant

This adds a WPT test for the case where a filter set on an inline
element should apply to a block-level descendant, even when the inline
ancestor has no inline children of its own. The CSS filter property
is non-inherited per css-filter-effects-1 — the descendants are not
"inheriting" the filter; the filter applies to the element together
with its painting subtree, which includes the block descendant and its
own inline grandchild.

The shape exercised is:
<a filter> → <div> → <span class="box">

With the bug, the inline &lt;a&gt; had a zero bounding box (RenderInline
with no inline children), so the source image was never built and the
descendant never rendered through the filter. It is now fixed in
WebKit, but no WPT test guarded the regression.

WebKit-Bug: <a href="https://bugs.webkit.org/show_bug.cgi?id=277228">https://bugs.webkit.org/show_bug.cgi?id=277228</a>
WebKit-Canonical-Link: <a href="https://commits.webkit.org/315788@main">https://commits.webkit.org/315788@main</a>
</pre>

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Component: web-platform-tests → Web Painting
Product: Testing → Core
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 398 tests and 5 subtests

Status Summary

Firefox

OK : 38
PASS: 1[GitHub] 23[Gecko-linux2204-64-wayland-debug, Gecko-linux2204-64-wayland-opt] 3016[Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt] 3302[Gecko-windows11-64-25h2-opt] 3305[Gecko-windows11-64-25h2-debug] 3308[Gecko-android-em-14-x86_64-debug-geckoview] 3310[Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview] 3312[Gecko-linux2404-64-debug, Gecko-linux2404-64-opt]
FAIL: 14[Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt] 55[Gecko-linux2404-64-debug, Gecko-linux2404-64-opt] 57[Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview] 59[Gecko-android-em-14-x86_64-debug-geckoview] 62[Gecko-windows11-64-25h2-debug] 65[Gecko-windows11-64-25h2-opt]

Chrome

PASS: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Status: NEW → RESOLVED
Closed: 6 days ago
Resolution: --- → FIXED
Target Milestone: --- → 162 Branch
You need to log in before you can comment on or make changes to this bug.