[Webkit-unassigned] [Bug 255772] New: REGRESSION (Safari 15): HTMLVideoElement exposing wrong currentTime when calling play() and pause() back-to-back
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Apr 21 02:41:44 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=255772
Bug ID: 255772
Summary: REGRESSION (Safari 15): HTMLVideoElement exposing
wrong currentTime when calling play() and pause()
back-to-back
Product: WebKit
Version: Safari 15
Hardware: All
OS: All
Status: NEW
Severity: Normal
Priority: P2
Component: Media
Assignee: webkit-unassigned at lists.webkit.org
Reporter: andreas.kogler at bitmovin.com
Created attachment 466028
--> https://bugs.webkit.org/attachment.cgi?id=466028&action=review
Testpage for reproduction
When calling `play()` and `pause()` in quick succession on an HTMLVideoElement after page load, the exposed `currentTime` jumps to a nonsensical value.
Looks like an internal timer gets exposed instead of the actual `currentTime`.
Reproduction steps:
1. Open a web-page that has an HTMLVideoElement `muted` and with any `src` (HLS or progressive) loaded
3. Open the console
4. Wait for 10 seconds
3. Call `play()` and `pause()` on the video element
4. Observe that the `currentTime` is now close to 10 (instead of 0); Note: if you wait 20 seconds in step 4, the `currentTime` is going to be close to 20 etc.
Issue starts to occur on Safari 15 and still exists in Safari 16. Also tested and verified same behaviour with Orion browser(WebKit 615.1.16.1).
The attached test-page executes all steps for you. It waits for 10 seconds and then calls `play()` and `pause()` back-to-back, logging the `currentTime` every 200ms.
--
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/20230421/06561d2f/attachment.htm>
More information about the webkit-unassigned
mailing list