| Summary: | REGRESSION(r286795): -webkit-mask-composite behaves differently with multiple masks | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Caleb <aquaductape> | ||||
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED DUPLICATE | ||||||
| Severity: | Normal | CC: | bfulgham, gsnedders, jensimmons, mattwoodrow, ntim, simon.fraser, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | Safari 15 | ||||||
| Hardware: | iPhone / iPad | ||||||
| OS: | iOS 15 | ||||||
| Attachments: |
|
||||||
|
Description
Caleb
2022-05-11 17:30:00 PDT
I forgot to mention, by broken, I mean the element where the mask image is applied to is no longer visible There are 2 issues here (thank you Matt for giving more details): 1. -webkit-mask-composite: source-in now computes to -webkit-mask-composite: source-in, source-in instead of -webkit-mask-composite: source-in, source-over for multiple gradients since r286795 2. -webkit-mask-composite: source-in/mask-composite: intersect has different behavior on a single gradient compared to other browsers, but this pre-dates r286795 (tested on an older computer) 1. can be fixed by restoring the old behavior for -webkit-mask-composite, but the testcase wouldn’t be fixed until 2. is fixed too, since it uses both prefixed and unprefixed versions. mask-composite behaves per-spec, the only possible action item here is change the prefixed version. *** Bug 241004 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 241541 *** |