[Webkit-unassigned] [Bug 280970] New: getUserMedia video track getSettings() returns stale value for torch constraint

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=280970

            Bug ID: 280970
           Summary: getUserMedia video track getSettings() returns stale
                    value for torch constraint
           Product: WebKit
           Version: Safari 18
          Hardware: iPhone / iPad
                OS: iOS 18
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Media
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: alex at pixelverse.ch

Calling getSettings() on a video track returns stale values for the `torch` constraint.

In previous versions (iOS 17 and earlier), getSettings() would return `false` for the `torch` constraint after a call to `applyConstraints({ advanced: [ { torch: true ]})` succeeded.
Since iOS 18, getSettings() will now return `false` instead.

This of course makes it hard to determine the current state of the flashlight based on the result of the `getSettings()` call.

Reproducer: https://github.com/pixelverse-llc/safari-ios18-gum-torch-setting
To reproduce: load index.html and wait for the video feed to appear. Press 'ON' to enable the flash, and observe that getSettings() returns `false` for `torch`. Press 'OFF' to disable the flash: getSettings() now returns `true`, the previous value.

The `torch` constraint can be used to toggle the camera flashlight on iOS devices (see: https://www.oberhofer.co/mediastreamtrack-and-its-capabilities/ for a write-up)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241007/c4b33599/attachment.htm>