[webkit-reviews] review granted: [Bug 232174] WebKit ought to be able to play videos without Content-Length HTTP header fields and without range support : [Attachment 442199] Patch

[bugzilla-daemon at webkit.org]

Geoffrey Garen <ggaren at apple.com> has granted Alex Christensen
<achristensen at apple.com>'s request for review:
Bug 232174: WebKit ought to be able to play videos without Content-Length HTTP
header fields and without range support
https://bugs.webkit.org/show_bug.cgi?id=232174

Attachment 442199: Patch

https://bugs.webkit.org/attachment.cgi?id=442199&action=review




--- Comment #2 from Geoffrey Garen <ggaren at apple.com> ---
Comment on attachment 442199
  --> https://bugs.webkit.org/attachment.cgi?id=442199
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?