[Webkit-unassigned] [Bug 224899] Unprefix -webkit-backdrop-filter

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=224899

--- Comment #9 from Karl Dubost <karlcow at apple.com> ---
Created attachment 461954

  --> https://bugs.webkit.org/attachment.cgi?id=461954&action=review

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220828/7c308014/attachment-0001.htm>