Bugzilla

This was reported in https://twitter.com/matthew_d_green/status/1527687593965518849, and I believe I know what's going on.

We've identified a situation where Google Meet works differently in Firefox vs Chrome:
1. The user joins a meeting *without* their AirPods on
2. then they open the case and put them on

In this situation, Meet auto-switches to the AirPods in Chrome (see toast message in the attached screenshot), but not in Firefox.

We suspect Meet holds off in Firefox because it might trigger a permission prompt, because by default we give per-device permissions in Firefox. An unprompted permission prompt could surprise a percentage of users, who might click Deny, ruining Meet's access to the AirPods in the current tab, which is a legitimate concern.

This seems like a good use case to finally implement bug 1609427. With that API, Meet could check that it has permission to the AirPods without inducing a prompt:
```js
const perm = await navigator.permissions.query({name: "camera", deviceId: headsetDeviceId});
if (perm.state == "granted") {
  proceedToSwitchToHeadset(headsetDeviceId);
}
```
This would fix it for the significant population of users who have already checked `☑ Remember this decision` for Meet.

This was reported in https://twitter.com/matthew_d_green/status/1527687593965518849, and I believe I know what's going on.

We've identified a situation where Google Meet works differently in Firefox vs Chrome:
1. The user joins a meeting *without* their AirPods on
2. then they open the case and put them on

In this situation, Meet auto-switches to the AirPods in Chrome (see toast message in the attached screenshot), but not in Firefox.

We suspect Meet holds off in Firefox because it might trigger a permission prompt, because by default we give per-device permissions in Firefox. An unprompted permission prompt could surprise a percentage of users, who might click Block, ruining Meet's access to the AirPods in the current tab, which is a legitimate concern.

This seems like a good use case to finally implement bug 1609427. With that API, Meet could check that it has permission to the AirPods without inducing a prompt:
```js
const perm = await navigator.permissions.query({name: "camera", deviceId: headsetDeviceId});
if (perm.state == "granted") {
  proceedToSwitchToHeadset(headsetDeviceId);
}
```
This would fix it for the significant population of users who have already checked `☑ Remember this decision` for Meet.

This was reported in https://twitter.com/matthew_d_green/status/1527687593965518849, and I believe I know what's going on.

We've identified a situation where Google Meet works differently in Firefox vs Chrome:
1. The user joins a meeting *without* their AirPods on
2. then they open the case and put them on

In this situation, Meet auto-switches to the AirPods in Chrome (see toast message in the attached screenshot), but not in Firefox.

We suspect Meet holds off in Firefox because it might trigger a permission prompt, because by default we give per-device permissions in Firefox. An unprompted permission prompt could surprise a percentage of users, who might click `Block`, ruining Meet's access to the AirPods in the current tab, which is a legitimate concern.

This seems like a good use case to finally implement bug 1609427. With that API, Meet could check that it has permission to the AirPods without inducing a prompt:
```js
const perm = await navigator.permissions.query({name: "camera", deviceId: headsetDeviceId});
if (perm.state == "granted") {
  proceedToSwitchToHeadset(headsetDeviceId);
}
```
This would fix it for the significant population of users who have already checked `☑ Remember this decision` for Meet.