W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2010

[whatwg] media resources: addressing media fragments through URIs spec

From: timeless <timeless@gmail.com>
Date: Sun, 4 Jul 2010 14:43:19 +0300
Message-ID: <AANLkTinW6TdP8dy3yF_l22X9A5v3HK8QgSmLUSRawu9R@mail.gmail.com>
On Sun, Jul 4, 2010 at 5:26 AM, silviapfeiffer1
<silviapfeiffer1 at gmail.com> wrote:
> It doesn't actually matter what element the URI appears in - your
> element has to deal with the data that it receives and if
> "file.ogv#t=1:00,1:15" is an Ogg Theora segment out of a video, then
> that is what the <img> element receives.

right.

> I am
> not aware though of any <img> element implementation that can deal
> with Ogg Theora video.

That's changeable. And you seem to be totally ignoring that this is
the thrust of someone else's request.

Note that I'm not the one asking for it. Just trying to explain it to
you since you seem to be doing a good job of totally missing the
point.

> If you are, however, asking to turn the Ogg Theora video into a APNG
> or a animated GIF or even a MNG, there will need to be a transcoding
> step at the server,

No no.

If a browser can decode a frame or sequence of frames from an ogg,
then it can display them, and since it can display various image
formats in <img> (jpg, gif, png, apng, potentially mng, and in future
geckos SVG), then someone (not me!) is merely suggesting that ogg be
another one, either as a single frame or an animated sequence.
Received on Sunday, 4 July 2010 04:43:19 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:24 UTC