### Beta/Release Uplift Approval Request * **User impact if declined**: Users have to clear permissions / stop active WebRTC devices multiple times before device permissions are fully cleared. This makes for a bad UX and could be a privacy issue, since users expect permissions to be revoked on the first click. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: Yes * **If yes, steps to reproduce**: See STR in comment 0. * **List of other uplifts needed**: None * **Risk to taking this patch**: Medium * **Why is the change risky/not risky? (and alternatives if risky)**: Medium risk since the patch changes how we revoke / stop WebRTC device permissions. However, we have good WebRTC test coverage and the code change is relatively small. * **String changes made/needed**:
Bug 1698513 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Beta/Release Uplift Approval Request * **User impact if declined**: Users have to clear permissions / stop active WebRTC devices multiple times before device permissions are fully cleared. This makes for a bad UX and could be a privacy issue, since users expect permissions to be revoked on the first click. The bug only affects devices shared with iframes. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: Yes * **If yes, steps to reproduce**: See STR in comment 0. * **List of other uplifts needed**: None * **Risk to taking this patch**: Medium * **Why is the change risky/not risky? (and alternatives if risky)**: Medium risk since the patch changes how we revoke / stop WebRTC device permissions. However, we have good WebRTC test coverage and the code change is relatively small. * **String changes made/needed**: