Bug 224899

<rdar://problem/77288624>

Do we know what blocks it being unprefixed?

<rdar://67696804>

The main issue of contention was https://github.com/w3c/fxtf-drafts/issues/53

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?

Yes.

Mozilla is re-enabling backdrop-filter in Firefox Nightly https://bugzilla.mozilla.org/show_bug.cgi?id=1578503#c28

Firefox 103 shipped backdrop-filter last month: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/103

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.

*** Bug 245839 has been marked as a duplicate of this bug. ***

*** Bug 205019 has been marked as a duplicate of this bug. ***

*** Bug 273311 has been marked as a duplicate of this bug. ***

Safari 18 comes with unprefixed backdrop filter: https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/#css

(In reply to Tim Nguyen (:ntim) from comment #13) > Safari 18 comes with unprefixed backdrop filter: > https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/#css No it doesn't. See here: https://github.com/mdn/browser-compat-data/issues/25914

Also please see: https://github.com/tailwindlabs/tailwindcss/issues/13844#issuecomment-2655993211 (Sorry for multiple messages.)

Could you file a bug if something isn't working?

(In reply to Tim Nguyen (:ntim) from comment #13) > Safari 18 comes with unprefixed backdrop filter: > https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/#css Actually my question should have been: Why is it hidden behind a "Testable" feature flag called "CSS Unprefixed Backdrop Filter"? It works if I enable the flag, but how many Safari 18 users will have a Testable flag enabled? 0.00001% maybe?