youennf

> If we think that it's OK for an UA to refuse to allow an application to prevent background fireworks Such a UA should have good reasons for not allowing...

> This will impose a support burden on applications, which could need to maintain maintain a camera blacklist. My understanding is that UAs are responsible for ensuring the results are...

@aboba, can you clarify whether this issue is a blocker for the CFC? AIUI, your suggestion seems like a request for API change, not a blocker for the API.

> it is likely to only be supported on new camera models AFAIK, iOS devices have cameras supporting this for quite some time. Coverage on this particular platform should be...

Option 1 is the most natural to me.

This relates to the proposal being made in https://github.com/w3c/mediacapture-extensions/pull/69.

1 is probably the easiest approach compared to 2 and is more natural than 3 and 4.

> * Can be serialized to bytes. (I assume this excludes Symbol) Agreed we need support to clone/postMessage metadata. I was thinking we could use structure cloning (https://html.spec.whatwg.org/multipage/structured-data.html#safe-passing-of-structured-data), which is...

> It might actually make sense to just drop down to JSON here I could see metadata be an array buffer, in which case JSON is not great. > I...

A single event seems better to me if we can stick to it. This event could contain information to identify which settings/capabilities have changed.