- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 May 2013 05:52:36 +0000
- To: public-texttracks@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22104
Bug ID: 22104
Summary: [WebVTT] Having a cue-setting keyword immediately
following cuetimes (without whitespace) seems to be
legal
Classification: Unclassified
Product: TextTracks CG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebVTT
Assignee: silviapfeiffer1@gmail.com
Reporter: caitlin.potter@senecacollege.ca
QA Contact: dave.null@w3.org
CC: mike@w3.org, public-texttracks@w3.org
According to
http://dev.w3.org/html5/webvtt/#dfn-collect-webvtt-cue-timings-and-settings,
the string immediately following the second webvtt timestamp is treated as
cuetimes, and that substring is split on whitespace. However this doesn't seem
to take the initial whitespace into account, therefore the following string:
`00:00.100 --> 00:05.000position:20% line:-3` is apparently totally legal.
It's not clear if this is intentional or not. Intuitively, it doesn't really
make sense to not include some kind of separator between the timestamp and
setting.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 21 May 2013 05:52:39 UTC