Bug 243546 - The camera and audio still works if User disables permissions for them in the middle of the WebRTC call
Summary: The camera and audio still works if User disables permissions for them in the...
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Safari 15
Hardware: iPhone / iPad iOS 15
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-08-04 08:45 PDT by Madara Freimane
Modified: 2022-08-17 02:11 PDT (History)
2 users (show)

See Also:


Attachments
sysdiagnose_2022.08.04_18-15-12+0300_iPhone-OS_iPhone_19G71.tar.gz (167.63 MB, application/x-gzip)
2022-08-04 08:45 PDT, Madara Freimane
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Madara Freimane 2022-08-04 08:45:33 PDT
Created attachment 461399 [details]
sysdiagnose_2022.08.04_18-15-12+0300_iPhone-OS_iPhone_19G71.tar.gz

Summary:
The camera and audio still works if User disables permissions for them in the middle of the WebRTC call

Tested devices:
Bug is reproducible on:
- iPhone 11 | iOS 15.6 (19G71)
- iPhone 13 | iOS 16 Beta 4 (20A5328h)

Scenario:
Precondition:
Safari browser is opened for the User
User has an active WebRTC call

Steps:
1. iOS User opens Website settings
2. iOS User disables (selects "Deny") "Camera" and "Microphone" permissions for the page

Actual result:
The camera and audio still works if User disables permissions for them in the middle of WebRTC call
(Changes for permissions are applied only after the page is reloaded)

Expected result:
The camera and audio do not work anymore if User disables permissions for them in the middle of WebRTC call

Reproducibility:
100%

Additional information:
-Bug is not reproducible with Android OS using different browsers.
-Log file added in attachments (defect reproduced with Google WebRTC sample on 04.08.22 at 18:15 CET)
Comment 1 Radar WebKit Bug Importer 2022-08-17 02:08:42 PDT
<rdar://problem/98772142>
Comment 2 youenn fablet 2022-08-17 02:11:54 PDT
This is a decision from Safari, I forwarded the information to the responsible team.
Closing this bug as moved.