Skip to main content
TestingPhone
Menu
2026-09-20Source: WebKit

Safari 27 Fixes Camera and Microphone Bugs That Matter for Browser Phone Tests

Safari 27 includes media-capture fixes for live microphone sessions, capture constraints, camera photo sequencing, track settings, and video orientation. Those changes can affect how browser diagnostics behave on iPhone.

Safari 27 chart showing the release is dominated by resolved issues and improved features
Image: WebKitEditorial image from the primary-source ecosystem
01

Safari 27 is a meaningful media-capture update

WebKit's Safari 27 release notes contain several fixes directly related to camera, microphone, and WebRTC behavior. For a normal browsing session these may be invisible. For a site that asks the browser to capture audio or video, they matter.

Safari 27 ships with iOS 27, so these fixes are directly relevant to browser-based phone testing on current iPhones.

02

Microphone capture should behave more predictably

WebKit says it fixed the WebProcess AudioSession so it remains active while microphone capture is live. It also changed OverconstrainedError to align better with the Media Capture specification and fixed a configuration-change event that could be lost while a MediaStreamTrack was muted.

For TestingPhone, the practical benefit is better separation between a browser/media-capture problem and an actual microphone symptom. A failed permission or capture path should never be mistaken for failed hardware.

03

Camera capture received fixes too

Safari 27 fixes ImageCapture request sequencing so takePhoto and applyConstraints do not reconfigure a capture session concurrently. WebKit also fixed a problem where transient device rotation could give captured video frames the wrong orientation.

The release notes also include a fix for MediaStreamTrack settings becoming incorrect when source settings changed during a track transfer. Those are implementation details, but they can surface as confusing behavior in real camera-testing interfaces.

04

What TestingPhone should do with this

The correct response is regression testing, not assuming Safari 27 makes every camera and microphone edge case disappear. TestingPhone should keep capability detection, clear permission states, and user-confirmed quality checks even when the browser becomes more reliable.

  • Recheck microphone start, stop, replay, and permission recovery on Safari 27.
  • Recheck front and rear camera switching.
  • Rotate the phone during a camera session and confirm orientation remains sensible.
  • Keep unsupported and permission-denied states separate from hardware failures.

Keep reading

Continue through the magazine.

Magazine front page →