- From: Brendan Long <self@brendanlong.com>
- Date: Wed, 18 Sep 2013 09:34:39 -0600
- To: Philip Jägenstedt <philipj@opera.com>
- CC: "HTML WG (public-html@w3.org)" <public-html@w3.org>
Received on Wednesday, 18 September 2013 15:35:16 UTC
On 09/18/2013 08:11 AM, Philip Jägenstedt wrote: > Hmm, this makes we wonder what the property for accessing the data is > supposed to be. If it's a string, then it requires that the UA at > least know what the encoding of the text is, which seems like it might > not be true. RawCue and exposing the data as a typed array .data > property seems OK to me. The other option is to base64-encode cues > which are of an unknown encoding, I guess? It seems like exposing the binary directly is a better solution, since we know it will be needed (for cues with unknown encoding, and for cues that don't have a text representation, like CEA708). I'd rather not use base64 encoding, since it adds what seems to be unnecessary complexity.
Received on Wednesday, 18 September 2013 15:35:16 UTC