#826: Background Blur API
Discussions
2023-03-27
Dan: Multi-stakeholder looks good - apple, google, intel.... and mozilla.
Yves: it's a transform stream - which is good - and they exclude detected faces - so easy to implement.
Dan: in their security & privacy questionnaire response they said there's no security & privacy considerations section currently in the spec. We should for one.]
Yves: fact that they are using transform streams looks good so looks good to me.
Dan: i suggest we set to proposed close and close at the plenary.
Dan: leaves comment and sets to proposed close
2023-04-10
We agree to close with satisfied with concerns : see https://github.com/w3ctag/design-reviews/issues/826#issuecomment-1502014618 for closing comment.
OpenedMar 20, 2023
こんにちは TAG-さん!
I'm requesting a TAG review of Background Blur API.
On the Web, due to a lack of a standardized JS API for Background Blur and widespread demand (specially on Video conferencing/ Streaming use cases), developers have no options but to use ML frameworks like Tensorflow.js and other WASM libraries to satisfy their customers. This Background Blur API gives developers a choice to use the native platform's API.
Further details:
You should also know that...
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify riju