Bug 259045 - REGRESSION (Safari 16.5): fMP4 HLS livestreams wrong playback start position
Summary: REGRESSION (Safari 16.5): fMP4 HLS livestreams wrong playback start position
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: Safari 16
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-07-10 02:18 PDT by Andreas Kogler
Modified: 2024-03-28 06:33 PDT (History)
7 users (show)

See Also:


Attachments
Testpage for reproduction + fake livestream (6.27 KB, application/zip)
2023-07-10 02:18 PDT, Andreas Kogler
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kogler 2023-07-10 02:18:35 PDT
Created attachment 466997 [details]
Testpage for reproduction + fake livestream

When playing an HLS livestream with fMP4 segments using native browser playback (i.e. setiing the HLS playlist as `src` of a HTML `video` element), one would expect the livestream to start playing back on the live edge (the right edge) and display the most recent video content.

This worked fine up until Safari 16.3, but in Safari 16.5 playback starts at the end of the DVR window (the left edge). Couldn’t test it with Safari 16.4, so maybe it’s already broken there.

Interestingly, the issue does not occur when the HLS stream contains MPEG-TS segments instead of fMP4.

I have attached a test-page as well as a “fake livestream” to reproduce the issue, but any HLS livestream with fMP4 segments should surface the described issue.
Comment 1 Radar WebKit Bug Importer 2023-07-10 12:51:36 PDT
<rdar://problem/112033261>
Comment 2 Radosław Włodkowski 2023-09-14 07:44:32 PDT
We're experiencing exactly the same. Any update on this one?
Comment 3 Eric Carlson 2023-09-15 06:26:46 PDT
(In reply to Radosław Włodkowski from comment #2)
> We're experiencing exactly the same. Any update on this one?

This is a bug in a framework below WebKit. The team responsible for that framework is actively investigating it.
Comment 4 Lucky Goyal 2024-01-31 03:33:54 PST
Is there any further update on this bug please?
Comment 5 Lucky Goyal 2024-03-28 06:33:54 PDT
Hi Team, we observe that issue does not happen with Safari 17.4.1. Can you please confirm if a fix was done to address this issue?