- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 7 Jul 2015 21:56:24 +1200
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: WHATWG <whatwg@whatwg.org>, Andrew Scherkus <scherkus@chromium.org>
On Tue, Jul 7, 2015 at 9:41 PM, Philip Jägenstedt <philipj@opera.com> wrote: > Unsurprisingly, I like this, as it's basically what Presto did. However, I > think preload="metadata" should reach HAVE_CURRENT_DATA, because you do > want to decode the first frame. The naming mismatch is weird, but oh well. > OK. > > The question is, would Chrome(ium) be willing to implement that > reasonably > > quickly? I'm not optimistic given the canplaythrough debacle... > > Do you have links to previous debacles, so that I can see what the > constraints are, or have been? The constraint just seems to be a lack of interest in fixing interop issues in this area: http://code.google.com/p/chromium/issues/detail?id=73609 > Given that Blink's default preload state is > auto that ought to limit the breakage somewhat, but I wouldn't really be > surprised to find sites that use preload="metadata" and yet assume that > canplay will fire, or similar. > > Whatever kind of mess we're in, it would be nice to aim for > interoperability. > Indeed. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn
Received on Tuesday, 7 July 2015 09:56:59 UTC