W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2011

Re: Feedback on MediaController

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 26 Apr 2011 19:28:10 +0000 (UTC)
To: Philip Jägenstedt <philipj@opera.com>
cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <Pine.LNX.4.64.1104261927120.25791@ps20323.dreamhostps.com>
On Tue, 26 Apr 2011, Philip Jägenstedt wrote:
> On Thu, 21 Apr 2011 01:01:53 +0200, Ian Hickson <ian@hixie.ch> wrote:
> > On Mon, 18 Apr 2011, Philip Jägenstedt wrote:
> > > 
> > > Apart from this, I think that TrackList really should be a list of 
> > > Track objects or similar, so that getName/getLanguage are pushed 
> > > onto that object as .name and .language, just like on TextTrack.
> > 
> > This would balloon the number of objects in the platform. Unless 
> > there's a very good reason to have objects for each of these tracks, 
> > we should avoid doing that.
> 
> Is it the number of interfaces that pollute the global (window) 
> namespace you are worried about, or the number of ECMAScript objects at 
> runtime?

Both, as well as overall complexity of the platform.


> Why would it a problem to have one object per audio/video track 
> but not a problem for text tracks?

It _is_ a problem for text tracks, it's just that they have much more 
stuff going on such that it makes more sense to give them objects than to 
not give them objects.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 26 April 2011 19:28:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:19 UTC