[Bug 10770] New: Should it really be OK to have timestamps with trailing garbage like <00:01.500b0rk>?

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

           Summary: Should it really be OK to have timestamps with
                    trailing garbage like <00:01.500b0rk>?
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#web
                    srt-cue-text-parsing-rules
        OS/Version: other
            Status: RESOLVED
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, philipj@opera.com


Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philipj@opera.com

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |FIXED

Section:
http://www.whatwg.org/specs/web-apps/current-work/complete.html#websrt-cue-text-parsing-rules

Comment:
Should it really be OK to have timestamps with trailing garbage like
<00:01.500b0rk>?

Posted from: 83.218.67.122

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2010-09-27 14:54:23 UTC ---
This is about the Otherwise branch of the "If token is a start tag" section of
the WebSRT cue text parser.

Since there is no check of the position after successfully collecting a WebSRT
timestamp, something like <00:01.500b0rk> will slip through, which probably
isn't intended.

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-29 18:50:42 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

-- 
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 Wednesday, 29 September 2010 18:50:45 UTC