On Thu, 16 Jul 2009, Jeff Walden wrote:
(For the few authors who really want to go crazy, they can already
overlap HTML onto theirvideo and do whatever crazy stuff they want
to do.)
By way of a use case for at least color and positioning, there's a
certain part of the third (?)
On 17.7.09 02:15, Ian Hickson wrote:
I think this particular case can be a victim of the 80% rule.
Fair enough, probably.
Jeff
On Fri, Jul 17, 2009 at 4:15 AM, Ian Hicksoni...@hixie.ch wrote:
On Thu, 16 Jul 2009, Jeff Walden wrote:
(For the few authors who really want to go crazy, they can already
overlap HTML onto theirvideo and do whatever crazy stuff they want
to do.)
By way of a use case for at least color
On 17/7/09 15:04, Tab Atkins Jr. wrote:
On Fri, Jul 17, 2009 at 4:15 AM, Ian Hicksoni...@hixie.ch wrote:
On Thu, 16 Jul 2009, Jeff Walden wrote:
(For the few authors who really want to go crazy, they can already
overlap HTML onto theirvideo and do whatever crazy stuff they want
to do.)
By
On 15.7.09 17:56, Ian Hickson wrote:
On Thu, 19 Feb 2009, Ian Fette wrote:
However, there's a lot of uses for subtitles / captions that cannot be
met with subrip. No styling (beyond the bare basics), no karaoke
commands, no alpha, no nice handling for collisions, margins, shadow
colors,
On Thu, 19 Feb 2009, Greg Millam wrote:
Here is my proposal: [...]
I think this proposal is a good direction to go in. However, I think it is
still too early to put this in HTML5, and based on the quality of
implementations so far, it will probably still be too early by the time
HTML5 goes
Greg Millam wrote:
* All timed text tracks encoded in the video file are added to the
list, as an implicit caption element.
I'm not entirely sure what you mean, but I don't think implying a new
element in the HTML based on text tracks within the media file is a good
idea, and nor is it
On 20.2.09 05:54, Lachlan Hunt wrote:
Greg Millam wrote:
* All timed text tracks encoded in the video file are added to the
list, as an implicit caption element.
I'm not entirely sure what you mean, but I don't think implying a new
element in the HTML based on text tracks within the media
Instead of
* getCaptionList(): returns an array of caption elements.
Have
* getCaptions(): returns an array of caption elements.
Greg,
I think that it's important that there be something that everyone can depend
on being present across all UAs, so I commend your dedication here. I think
adding subrip as a baseline is a great idea so that everyone knows that
there's something that works everywhere, and subrip is dead simple.
Greg -
Interesting ideas! A few questions that occur to me on first read:
On Feb 19, 2009, at 2:37 PM, Greg Millam wrote:
HTML5 / Page Author:
* Each video will have a list of zero or more Timed Text tracks.
* A track has three variables for selection: Type, Language, Name.
These can be
On Feb 20, 2009, at 00:37, Greg Millam wrote:
The current state of accessibility and captions in HTML5 has been
relegated to http://wiki.whatwg.org/wiki/Video_accessibility - a wiki
page with use cases, requirements, existing solutions, and an empty
Proposed Solutions category.
Since then,
12 matches
Mail list logo
