Bug 239067 - REGRESSION (Safari 15.4): Multiple activeCues observed on cueChange event for id3 type
Summary: REGRESSION (Safari 15.4): Multiple activeCues observed on cueChange event for...
Status: RESOLVED DUPLICATE of bug 237630
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: Safari 15
Hardware: Mac (Intel) macOS 11
: P2 Blocker
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-04-11 05:59 PDT by Ashutosh Kumar
Modified: 2022-04-27 01:33 PDT (History)
4 users (show)

See Also:

Attachments
I have attached screenshot for the active cues seen in different browser version (324.78 KB, image/png)
2022-04-12 07:32 PDT, Ashutosh Kumar 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ashutosh Kumar 2022-04-11 05:59:27 PDT 
This issue is Observed only after the latest update of the safari to Version 15.4 (16613.1.17.1.13, 16613)

I am observing multiple active cues on cueChange event on the latest safari version only for the id3 subtitle type.
Previously i.e, safari version less than 15.4 i used to see only one active cue for a particular time range.

EG Safari < 15.4:

Let's assume we have id3 subtitle displaying text "Hello" from 
startTime -  1 sec 
endTime-  5 sec

We used to get one active cue for this time range.


Now Safari 15.4:

We are always getting multiple active cue for this time range.

Can you please let us know this issue is due to any latest update in the safari?
Comment 1 Ashutosh Kumar 2022-04-12 07:32:45 PDT 
Created attachment 457330 [details]
I have attached screenshot for the active cues seen in different browser version
Comment 2 Radar WebKit Bug Importer 2022-04-12 14:55:54 PDT 
<rdar://problem/91650982>
Comment 3 Eric Carlson 2022-04-19 06:47:21 PDT 
This was caused by http://webkit.org/b/229924, but it should be fixed by http://webkit.org/b/237630

*** This bug has been marked as a duplicate of bug 237630 ***
Comment 4 shivaksk1 2022-04-27 01:33:45 PDT 
Hi, could you please let me know in when (and which Safari version) this fix will be available?