#826: Background Blur API

Visit on Github.

Opened Mar 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.

  • Explainer : explainer
  • Specification URL: spec url
  • Tests: wpt
  • User research:
  • Security and Privacy self-review: url
  • GitHub repo: repo
  • Primary contacts
  • Organization(s)/project(s) driving the specification: Intel, Google, Apple. WebRTC.
  • Key pieces of existing multi-stakeholder review or discussion of this specification: reviews + WebRTC meetings minutes.
  • External status/issue trackers for this specification Chrome Status

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: planning Origin Trial (chrome) end of march.
  • The group where the work on this specification is currently being done: WebRTC
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WebRTC
  • Major unresolved issues with or opposition to this specification: None

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

Discussions

2023-03-27

Minutes

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

Minutes

We agree to close with satisfied with concerns : see https://github.com/w3ctag/design-reviews/issues/826#issuecomment-1502014618 for closing comment.