RESOLVED FIXED 224899
Unprefix -webkit-backdrop-filter
https://bugs.webkit.org/show_bug.cgi?id=224899
Summary Unprefix -webkit-backdrop-filter
Tim Nguyen (:ntim)
Reported 2021-04-21 15:31:48 PDT
Would be nice to ship it unprefixed. There are some WPT that could imported in css/filter-effects.
Attachments
issue 53 - rendering in Safari, firefox, chrome (570.98 KB, image/png)
2022-08-28 16:41 PDT, Karl Dubost
no flags
Radar WebKit Bug Importer
Comment 1 2021-04-28 15:32:14 PDT
Sam Sneddon [:gsnedders]
Comment 2 2021-08-13 10:13:50 PDT
Do we know what blocks it being unprefixed?
Sam Sneddon [:gsnedders]
Comment 3 2021-10-25 04:19:08 PDT
Simon Fraser (smfr)
Comment 4 2021-10-25 10:24:10 PDT
The main issue of contention was https://github.com/w3c/fxtf-drafts/issues/53
Sam Sneddon [:gsnedders]
Comment 5 2021-10-25 10:50:23 PDT
Is this (https://github.com/w3c/fxtf-drafts/issues/53#issuecomment-500010730) comment from Tab still the current status: > Yeah, the core idea is that unless/until WK actually describes their behavior, which they were tasked with doing at the last meeting, we're going with the current spec (Chrome) behavior. And if they don't do that reasonably quickly, Firefox will likely follow the spec, and begin fully locking in that behavior. So the status quo is this bug (unprefixing the property) is blocked on a task to spec our behaviour?
Simon Fraser (smfr)
Comment 6 2021-10-25 11:47:42 PDT
Yes.
Karl Dubost
Comment 7 2022-06-09 07:53:59 PDT
Mozilla is re-enabling backdrop-filter in Firefox Nightly https://bugzilla.mozilla.org/show_bug.cgi?id=1578503#c28
Šime Vidas
Comment 8 2022-08-21 05:29:53 PDT
Firefox 103 shipped backdrop-filter last month: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/103
Karl Dubost
Comment 9 2022-08-28 16:41:02 PDT
Created attachment 461954 [details] issue 53 - rendering in Safari, firefox, chrome Let's see. > There are some WPT that could imported in css/filter-effects. Currently there are a number of backdrop-filter tests which are failing in Safari TP 152 https://wpt.fyi/results/css/filter-effects?label=master&label=experimental&aligned&view=subtest&q=css%2Ffilter-effects A number of them would pass if backdrop-filter was unprefixed. They seem to be imported already https://searchfox.org/wubkat/search?q=backdrop-filter&path=imported%2Fw3c%2Fweb-platform-tests%2Fcss%2Ffilter-effects&case=false&regexp=true and most of them marked as FAIL. In Comment #5, the ship has sailed. > So the status quo is this bug (unprefixing the property) is blocked on a task to spec our behaviour? Both Chrome and Firefox are shipping the property unprefixed. The current spec is https://drafts.fxtf.org/filter-effects-2/#BackdropFilterProperty One of the issues which was given is illustrated in https://github.com/w3c/fxtf-drafts/issues/53#issuecomment-451599226 https://jsbin.com/firinoy/edit?html,output See the screenshot issue 53 - rendering in Safari, firefox, chrome Only WebKit behaves differently. What would be good to understand is how many tests are failing/passing when unprefixing with the current implementation which depends on Core Animation. The last comment on the issue 53 was made on Dec 23, 2019 (almost 3 years ago). I wonder if Dean or Myles have an opinion on the path forward here.
Oriol Brufau
Comment 10 2022-10-03 12:14:28 PDT
*** Bug 245839 has been marked as a duplicate of this bug. ***
Matt Woodrow
Comment 11 2023-09-19 17:24:42 PDT
*** Bug 205019 has been marked as a duplicate of this bug. ***
Tim Nguyen (:ntim)
Comment 12 2024-04-26 11:17:17 PDT
*** Bug 273311 has been marked as a duplicate of this bug. ***
Tim Nguyen (:ntim)
Comment 13 2024-08-04 16:30:32 PDT
Note You need to log in before you can comment on or make changes to this bug.