W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2012

[Bug 15492] <track> Normalization for setter of TextTrackCue.text is not defined

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Feb 2012 07:49:15 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Rufnf-0005KW-10@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15492

--- Comment #3 from Fredrik S <fs@opera.com> 2012-02-07 07:49:14 UTC ---
I mean "normalization" as in what's defined in
http://dev.w3.org/html5/webvtt/#webvtt-parser-algorithm step 1. I.e:

'\0' -> U+fffd
'\r\n' -> '\n'
'\r' -> '\n'

It occurred to me that it may be weird if one of the paths (the one through the
VTT parser) had well-formed/normalized input while the other two
(TextTrackCue.text and the TextTrackCue constructor) did not. The cue text
tokenization/parsing algorithm itself will probably handle it, but the result
will be different for the same input depending on the way it took through the
parser.

An example might be anything with an embedded '\0':

<i>F\0oo</i>

which when parsed via a track-file would give:

<i>
 +-"F\xfffdoo"

while through cue.text it would render:

<i>
 +-"F\0oo"

-- 
Configure bugmail: https://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 Tuesday, 7 February 2012 07:51:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 7 February 2012 07:51:06 GMT