Bug 207489

Summary: video.currentTime is not being updated in iOS 13.4 Beta
Product: WebKit Reporter: Christoph Bartschat <christoph>
Component: WebRTCAssignee: Eric Carlson <eric.carlson>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, eric.carlson, ews-watchlist, glenn, hta, jer.noble, jonlee, philipj, sergio, tommyw, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: Safari 13   
Hardware: iPhone / iPad   
OS: iOS 13   
Attachments:
Description Flags
Source code for repro
none
Patch none

Description Christoph Bartschat 2020-02-10 11:47:58 PST
Created attachment 390276 [details]
Source code for repro

Safari appears to never increment the currentTime property of the video element from a getUserMedia stream in iOS 13.4 Beta.

A basic repro case can be viewed on an iPhone here: 8th.io/y8k4p

The repro app does the following:
* getUserMedia -> stream -> video
* Print out videoHeight, videoWidth, and currentTime of the video

We tested this with an iPhoneXR with iOS 13.4 Beta.

Source code for the repro is attached.
Comment 1 Radar WebKit Bug Importer 2020-02-10 13:11:20 PST
<rdar://problem/59322640>
Comment 2 Jon Lee 2020-02-10 15:14:54 PST
I'll ask the obvious: this is a regression from iOS 13.3?
Comment 3 Christoph Bartschat 2020-02-10 16:01:47 PST
Yes, this is a regression observed in 13.4. We see that 13.3.1 is working as expected.
Comment 4 Eric Carlson 2020-02-11 10:27:25 PST
This was caused by r251566.
Comment 5 Eric Carlson 2020-02-11 10:41:03 PST
Created attachment 390388 [details]
Patch
Comment 6 WebKit Commit Bot 2020-02-11 13:14:49 PST
Comment on attachment 390388 [details]
Patch

Clearing flags on attachment: 390388

Committed r256346: <https://trac.webkit.org/changeset/256346>
Comment 7 WebKit Commit Bot 2020-02-11 13:14:50 PST
All reviewed patches have been landed.  Closing bug.
Comment 8 Christoph Bartschat 2020-02-19 14:59:03 PST
Is this fix expected to have been propagated to the latest iOS 13.4 Beta 2? We're still seeing the same issue after updating.
Comment 9 Eric Carlson 2020-02-19 15:58:53 PST
(In reply to Christoph Bartschat from comment #8)
> Is this fix expected to have been propagated to the latest iOS 13.4 Beta 2?
> We're still seeing the same issue after updating.

No, the fix missed the cutoff for Beta 2.