- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sun, 12 Oct 2014 22:24:00 +1100
- To: Jon Piesing <Jon.Piesing@tpvision.com>
- Cc: "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Alexander Adolf <alexander.adolf@condition-alpha.com>
On Sun, Oct 12, 2014 at 10:21 PM, Jon Piesing <Jon.Piesing@tpvision.com> wrote: > On 12 Oct 2014 21:48, "Jon Piesing" <Jon.Piesing@tpvision.com> wrote: > >>> >>> Sylvia, >>> >>> On Sun, Oct 12, 2014 at 5:39 PM, Silvia Pfeiffer >>> <silviapfeiffer1@gmail.com> wrote: >>> <snip> >>> > The relevant angle here is the Web, since we're in the W3C. When you >>> > use a Web browser or a Web browser's rendering engine to render video, >>> > you have to ascertain that it still fits within the limitations of the >>> > Web platform and its technologies. That's all really. >>> >>> That's one perspective. Another perspective is that the web browser is >>> just controlling a media player provided by the platform which has an >>> existence outside the Web platform. > > >>That's not how html5 video works. The player is part of the browser, not a >> separate application. > > > The embedded browsers that I know all call a media player library (not > application) provided by the platform - the same media player library used > by other features of the platform. A library is not a player: the only interface you're seeing is still the Web interface, so that doesn't change what I said earlier. Regards, Silvia.
Received on Sunday, 12 October 2014 11:24:47 UTC