W3C home > Mailing lists > Public > public-html-a11y@w3.org > November 2010

Re: [minutes] Media sub-team teleconference: Oct. 27, 2010

From: Eric Carlson <eric.carlson@apple.com>
Date: Tue, 02 Nov 2010 21:22:16 -0700
Cc: Sean Hayes <Sean.Hayes@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <746EEBA9-A020-4C07-B9DB-88CF3E35AE27@apple.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>

On Nov 2, 2010, at 9:01 PM, Silvia Pfeiffer wrote:

> I think we need to find a solution for how to add the positioning
> rules on cues. Maybe we can go with existing CSS technology? Could CSS
> settings be used here, just like on a <div> element? Do we even need a 
> CueSettings attribute?
> 
  I agree that we need to figure describe cue position before this is added to the spec. CSS seems like the logical way to do it, though I don't have any concrete suggestions.

eric



> 
> 
> On Wed, Nov 3, 2010 at 2:35 AM, Sean Hayes <Sean.Hayes@microsoft.com> wrote:
>> I'm aware I didn't define CueSettings, I'm not sure what the convention for that would be, so I'll get to that later..
>> 
>> TimedtrackCue at the end is a repeat and can be ignored.
>> 
>> -----Original Message-----
>> From: Eric Carlson [mailto:eric.carlson@apple.com]
>> Sent: 02 November 2010 15:21
>> To: Sean Hayes
>> Cc: HTML Accessibility Task Force
>> Subject: Re: [minutes] Media sub-team teleconference: Oct. 27, 2010
>> 
>> Hi Sean -
>> 
>> On Nov 2, 2010, at 7:51 AM, Sean Hayes wrote:
>> 
>>> In fulfillment of my action item, attached are the proposed edits I believe are required to make the current HTML5 technology neutral wrt WebSRT.
>>> 
>>  The "TimedTrackCue" section at the end of the document is empty, and you don't define "CueSettings". Did you send the correct version of the document?
>> 
>> eric
>> 
>> 
>> 
>> 
>> 
Received on Wednesday, 3 November 2010 04:23:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:23 GMT