1205644 - firefox ignores video track element when injecting it

Status: RESOLVED DUPLICATE of bug 1242599

(Core :: Audio/Video: Playback, defect, P3)

Description

[tomati]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36

Steps to reproduce:

see fiddle: https://jsfiddle.net/5vko6nby/2/


Actual results:

no text tracks where added


Expected results:

text tracks should be added

Comment 1

[tomati]

this happens also with vtt file from same domain, so no cross origin problem.
fiddle gives true in chrome and false in firefox

Comment 2

[tomati]

i my special implementation, the fix was to move the load between adding sources and tracks instead of doing that after:


this.createVideoSourceElements();
this.video_element_raw.load();
this.createVideoTrackElements();
//this.video_element_raw.load();

Comment 3

[David Flanagan [:djf]]

In my investigation of bug 1214027, I found that textTrack is updated asynchronously. If you add a setTimeout() call after you add the <track> element and before querying the textTrack property, your code will work the way you expect it to.

I don't know if that resolves the bug or not, however.

Comment 4

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Mass change P2 -> P3

Comment 6

[Boris Zbarsky [:bzbarsky]]

How is this a duplicate?  Everything here is in a document, no?

Comment 7

[Benjamin Chen [:bechen]]

(In reply to Boris Zbarsky [:bz] from comment #6)
> How is this a duplicate?  Everything here is in a document, no?

The "in a document at bug 871747"  means that the TrackElement is bind to the dom tree.
After some fixes, the TrackElement can work normally if it has a MediaElement parent, bind to the dom tree is not mandatory.

Comment 8

[Boris Zbarsky [:bzbarsky]]

Yes, but in this bug's testcases it's always bound to a DOM tree, no?  So how are they related to bug 871747?

Comment 9

[Benjamin Chen [:bechen]]

(In reply to Boris Zbarsky [:bz] from comment #8)
> Yes, but in this bug's testcases it's always bound to a DOM tree, no?  So
> how are they related to bug 871747?

hmm, I read the testcase again, Bug 1242599 fix the asynchronous issue in comment 3. So this bug should mark as duplicate to 1242599.

Comment 10

[Boris Zbarsky [:bzbarsky]]

Is the actual testcase for this bug fixed?

Comment 11

[Benjamin Chen [:bechen]]

(In reply to Boris Zbarsky [:bz] from comment #10)
> Is the actual testcase for this bug fixed?

Yes, I ran nightly to verify the testcase yesterday.