| Summary: | REGRESSION (Safari 16.4): HTMLVideoElement reports currentTime outside buffered range | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Andreas Kogler <andreas.kogler> | ||||
| Component: | Media | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED CONFIGURATION CHANGED | ||||||
| Severity: | Normal | CC: | eric.carlson, jer.noble, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | Safari 16 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
This doesn't reproduce for me with current sources. The currentTime is 0 when the buffered ranges is [0 - 0], stays at 0 when it jumps to [0 - 3.92], changes to 0.000001 when the buffered ranges changes to [0.000001 - 3.92], and stays at 0.000001 when the 'durationchanged' event fires and the buffered ranges changes to [0.000001 - 171.92] I believe it was fixed by the changes for https://bugs.webkit.org/show_bug.cgi?id=255185 and/or https://bugs.webkit.org/show_bug.cgi?id=257400 |
Created attachment 467021 [details] Testpage + stream for reproduction Here is a test page where the video element reports a currentTime of 0.00001 and a buffered range of 0-3.9. After some time a durationchanged event is fired and the buffered range jumps to 0.43 - 187 while the currentTime stays at 0.00001. After this happens the video still is able to play from 0, effectively playing outside of all buffered ranges. This starts to happen with Safari 16.4 and didn't occur up until Safari 16.3. Check out the attached test setup for reproduction.