Bug 262618 - REGRESSION (iOS 17): Browser changes video stream track constraints (width, height, aspect ratio) regardless of requested constraints
Summary: REGRESSION (iOS 17): Browser changes video stream track constraints (width, h...
Status: RESOLVED DUPLICATE of bug 259364
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: Safari 17
Hardware: iPhone / iPad iOS 17
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-10-04 08:31 PDT by Zach Rattner
Modified: 2023-11-10 02:50 PST (History)
4 users (show)

See Also:

Attachments
Screen orientation changes causing UI issues in iOS 17 (4.91 MB, video/mp4)
2023-10-04 08:31 PDT, Zach Rattner 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zach Rattner 2023-10-04 08:31:24 PDT 
Created attachment 468063 [details]
Screen orientation changes causing UI issues in iOS 17

We are seeing a new issue in iOS 17 where requested constraints (width, height, aspect ratio) are being ignored. This happens in two scenarios: 

1. On video stream initialization
2. On device orientation change

The issue only affects the display in the UI. If you record video, the resulting file is not distorted. But if you do not handle iOS 17 specifically, code that used to work in iOS 16 results in a bad UI. See attached video as an example.

It looks like the browser makes a copy of the track and changes its parameters at its discretion. It is possible to work around this in the UI, but some more info on whether this change in behavior was expected or a bug would be helpful.
Comment 1 Zach Rattner 2023-10-04 10:01:58 PDT 
@youennf Curious if you are already aware of this?
Comment 2 Radar WebKit Bug Importer 2023-10-04 11:58:47 PDT 
<rdar://problem/116478146>
Comment 3 youenn fablet 2023-11-10 02:50:41 PST 
Thanks Zach, I believe this will be fixed by PR for bug 259364.

*** This bug has been marked as a duplicate of bug 259364 ***