W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14510] <track> how should language be normalized?

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Oct 2011 09:06:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RIzR1-0007lJ-I4@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14510

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NEEDSINFO                   |INVALID

--- Comment #3 from Philip Jägenstedt <philipj@opera.com> 2011-10-26 09:06:07 UTC ---
(In reply to comment #2)

> How the conversion is done for in-band tracks depends on the specification that
> defines how to map that format to the HTML API.

Very well, I'll revisit the issue when such specs appear and need to be
implemented. (I'm assuming they'll be hand-wavy about the issue.)

> For out-of-band tracks, the spec seems unambiguous that the literal value in
> the attribute or API is left unmodified.
> 
> Is there something I can do in the spec to make this clearer? What led you to
> thinking this might not be the case?

When I filed the bug I was unable to find any spec language saying how to make
HTMLTrackElement.srclang to TextTrack.language at all, but I think this is it:
"The text track language is the element's track language, if any, or the empty
string otherwise."

Changing to INVALID.

-- 
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, 26 October 2011 09:06:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC