Rick Byers

One possibility for (1) is to define an error code that we always use for such cases of the platform rejecting without showing the user any UI. Separating platform non-support...

Discussed in the call today. Our implementation today doesn't require developers to specify a `mediation`, which is how we want to keep it. So updating the title to reflect that...

Note there's an [Intent to Ship for this in Chromium](https://groups.google.com/a/chromium.org/g/blink-dev/c/uNUWZ14SYJI/m/7-_h1rCXAQAJ). Definitely we prefer to see this in a venue with good IPR etc, but we need a signal of interest...

Yes agreed. IMHO our spec should talk only about "permission" not "consent".

I'm hitting this as well with Dorado 0.7.3+6e6c45cd on MacOS. I have restarted with `--no-trim` instead of `--trim adapters` and will follow up here on whether or not that fixed...

The argument that sites may misuse this API is, I think, the same argument for any powerful API: notifications, fullscreen, storage, autoplaying audio, even things we don't mediate well today...

I only have a little context in this topic and will have to get caught up with the positions of other experts in Chrome, especially around security. But I wanted...

For the record, I'm supportive of this for chromium and pretty sure it would pass an I2S (though we'll need a spec change to go through the formal process). Yes...

Searching chromium code it's unfortunately not likely we can come up with an exhaustive list, but [this](https://source.chromium.org/search?q=k%5Ba-zA-Z0-9%5D*Scheme.*%3D.*%5C%22%20file:.cc%20file:.h%20-file:out%2F%20-file:test&ss=chromium&start=1) seems to be a pretty good superset. There's a bunch of obscure things,...

As you can see from the link I shared, it looks like we have some ChromeOS-specific ones. Frankly, my hunch is that it's not worth adding any of them and...