Open Bug 1319687 Opened 8 years ago Updated 2 years ago

Fire 'canplaythrough' aggressively after loading first frame

Categories

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

defect

Tracking

()

Webcompat Priority P3

People

(Reporter: jwwang, Unassigned)

References

Details

Some sites expect 'canplaythrough' to start playback. We should switch readyState to HAVE_ENOUGH_DATA after loading first frame to fire 'canplaythrough'.
This also reduce the chance that some sites work on Chrome but look broken on FireFox.
Assignee: nobody → jwwang
Priority: -- → P3
Which site would to that? sounds more like a evangelism to me... always switching to HAVE_ENOUGH_DATA when we won't be able to play without interruption would be breaking the specs.
https://cs.chromium.org/chromium/src/content/renderer/media/webmediaplayer_ms.cc?rcl=0&l=609 This is what Chrome does which doesn't seem to worry about breaking specs.
(In reply to Jean-Yves Avenard [:jya] from comment #2) > Which site would to that? Bug 1299609 comment 12. Bug 1308717 comment 1.
seems to me that it's the behaviour of preload=metadata we should change... Having said that, those sites were not spec compliant... not sure this is something we want to fix
Be pedantic when we can and be pragmatic when we have to. Sometimes those sites just conclude FF is broken and turn to Chrome before evangelism prevails.
Assignee: jwwang → nobody
Webcompat Priority: --- → ?
Webcompat Priority: ? → revisit
Severity: normal → S3

Ksenia, is the site linked still showing that issue?

Flags: needinfo?(kberezina)

Yeah, this is still an issue. Setting webcompat priority as P3 for now as we've only got one report.

Webcompat Priority: revisit → P3
Flags: needinfo?(kberezina)
You need to log in before you can comment on or make changes to this bug.