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

Re: Survey ready on Media Multitrack API proposal

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 03 Mar 2010 22:19:47 -0800
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Eric Carlson <eric.carlson@apple.com>, "Michael(tm) Smith" <mike@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <6AF92B75-CD05-4B98-AA6C-056CD764CCF5@apple.com>
To: Philip Jägenstedt <philipj@opera.com>

On Mar 3, 2010, at 9:08 PM, Philip Jägenstedt wrote:

> On Thu, 04 Mar 2010 11:45:43 +0800, Silvia Pfeiffer <silviapfeiffer1@gmail.com 
> > wrote:
>
>>
>> OK, I see the problem. I didn't consider that JavaScript converts  
>> sees
>> no difference in [2] and ["2"].
>>
>> I have no issue with removing the getter on namedItem. I don't think
>> it's important.
>> The other getter already does the index by number.
>
> I agree with removing it. The only reason it was there to begin with  
> was because the HTMLCollection interface was copied. The remaining  
> tracks.item(n) is not very useful as it is only a longer way of  
> writing tracks[n]. Is it really necessary to keep it for these  
> hypothetical non-ECMAScript languages that might implement the  
> interface?

Yes, it's necessary to keep it. And it's not hypothetical - WebKit  
includes bindings to non-JavaScript languages.

Regards,
Maciej
Received on Thursday, 4 March 2010 06:20:25 GMT

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