Main.WebVTTImpl History

Hide minor edits - Show changes to output

November 18, 2013, at 06:00 PM by 208.70.31.249 -
Changed line 3 from:
* the discussion was build on top of the following aspects:
to:
The discussion was build on top of the following aspects:
Deleted lines 5-6:
some preliminary notes:
Changed lines 17-28 from:
rendering is generally lagging in behind and probably not interoperable
vttregions aren't shipped anywhere in the end so far

test the very latest features
how to find out the lowest common denominator (the common features implemented) ?
when we can move forward with other web standard

do we want to think about version numbers for the spec?
that's what the recommendation track means: fixed feature set

for the webvtt files? versioning on the web hasn't been a great success
browsers don't care about version number
to:
Some other preliminary notes (before the discussion on the document):
* rendering is generally lagging in behind and maybe not interoperable
* vttregions aren't shipped anywhere in the end so far

* how to test the very latest features?
* how to find out the lowest common denominator (the common features implemented) ?

* do we want to think about version numbers for the spec? that's what the recommendation track means: fixed feature set

* for the webvtt files? versioning on the web hasn't been a great success
* browsers don't care about version number
Restore
November 18, 2013, at 05:57 PM by 208.70.31.249 -
Added lines 1-30:
!! WebVTT Implementation Status

* the discussion was build on top of the following aspects:
* https://docs.google.com/document/d/1wiRIzr3InNuf2Uc7Nq_mdVrF-XwZhViOrnDHSUqP-JQ/edit

some preliminary notes:

webkit/blink/presto
- started implementing at the same time (one and half year ago)
- basic support for the spec is everywhere
- ships in various versions

firefox
- doesn't ship in the default

ie
- ?

rendering is generally lagging in behind and probably not interoperable
vttregions aren't shipped anywhere in the end so far

test the very latest features
how to find out the lowest common denominator (the common features implemented) ?
when we can move forward with other web standard

do we want to think about version numbers for the spec?
that's what the recommendation track means: fixed feature set

for the webvtt files? versioning on the web hasn't been a great success
browsers don't care about version number
Restore