[Bug 14487] <track> accept more white space characters as cue timing separators

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14487

Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #12 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-10-29 10:20:50 UTC ---
(In reply to comment #9)
> I don't understand. What is it you are suggesting change, and why? As far as I
> can tell, the spec is as intended (authors are required to give one or more
> space or tabs between the timestamp and the -->, but the parser accepts spaces,
> tabs, and form feeds and does silent error-correction if the spaces are omitted
> entirely).

I guess this works as long as we insist on 3 digits for the milliseconds.
Resetting to RESOLVED-FIXED.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 29 October 2011 10:20:57 UTC