Bug 259045

Summary:

REGRESSION (Safari 16.5): fMP4 HLS livestreams wrong playback start position

Product:

WebKit

Reporter:

Andreas Kogler <andreas.kogler>

Component:

Media

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

daniel.weinberger, eric.carlson, felix.hochgruber, jer.noble, lucky.goyal, mattias.bergstrom, radoslaw.wlodkowski, steezeven, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

Safari 16

Hardware:

Unspecified

OS:

Unspecified

Attachments:

Description	Flags
Testpage for reproduction + fake livestream	none

Andreas Kogler

Reported 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.

Attachments
Testpage for reproduction + fake livestream (6.27 KB, application/zip) 2023-07-10 02:18 PDT, Andreas Kogler	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2023-07-10 12:51:36 PDT

<rdar://problem/112033261>

Radosław Włodkowski

Comment 2 2023-09-14 07:44:32 PDT

We're experiencing exactly the same. Any update on this one?

Eric Carlson

Comment 3 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.

Lucky Goyal

Comment 4 2024-01-31 03:33:54 PST

Is there any further update on this bug please?

Lucky Goyal

Comment 5 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?

Felix H.

Comment 6 2024-10-04 02:37:14 PDT

I can actually still reproduce the issue in Safari 17.6.

steezeven

Comment 7 2024-11-20 12:15:07 PST

This also is occurring in Safari 18 still. Is there any updates (In reply to Eric Carlson from comment #3) > (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. This also is occurring in Safari 18 still. Is there any updates available on this?

Note You need to log in before you can comment on or make changes to this bug.