| Summary: | WebKit ought to be able to play videos without Content-Length HTTP header fields and without range support | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Alex Christensen <achristensen> | ||||||
| Component: | New Bugs | Assignee: | Alex Christensen <achristensen> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | eric.carlson, ews-watchlist, ggaren, glenn, jer.noble, philipj, sergio, webkit-bug-importer | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Alex Christensen
2021-10-22 14:04:32 PDT
Created attachment 442199 [details]
Patch
Comment on attachment 442199 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=442199&action=review r=me > Source/WebCore/ChangeLog:10 > + AVFoundation doesn't like it when you give it a range like 0-1/* because it doesn't know the content length. > + To work around this, wait until the entire video is loaded then respond with a known length. > + This isn't great, but it's better than not playing the video at all. So, was the old behavior a race condition based on how fast the video loaded? How did this every work at all? Created attachment 442376 [details]
Patch
It never did work. Committed r284816 (243508@main): <https://commits.webkit.org/243508@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 442376 [details]. |