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

Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear"

From: Joe D Williams <joedwil@earthlink.net>
Date: Mon, 12 Apr 2010 05:03:29 -0700
Message-ID: <EF507891681744DBAF29269964326BA2@joe1446a4150a8>
To: "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>
Cc: "Sean Hayes" <Sean.Hayes@microsoft.com>, "public-html" <public-html@w3.org>

Silvia Sent: Sunday, April 11, 2010 11:21 PM


> On Mon, Apr 12, 2010 at 12:55 PM, Joe D Williams 
> <joedwil@earthlink.net> wrote:
>>> The choice of @name is on purpose to avoid clashing with @title,
>>
>> That is a fine reason but @name is already used in other markup for 
>> embedded
>> content. Existing use of @name seems more associated with and used 
>> more like
>> @id since it seems to be moving towards associating with some sort 
>> of
>> context identification. Anyway, I would say that @name is already 
>> taken for
>> I would consider a different purpose.
>
> What other markup are you referring to that is already using @name?

<iframe> and <object> at least.
<a>?

> @name is not a global attribute like @id or @title (see
> http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#global-attributes).

True

> It has a different meaning with every element.

I don't think so. In existing uses @name names a context

> So, it is perfectly fine to use it here IMO.

Not perfectly fine, I think, because the attribute named @name already 
has a defined purpose ame everywhere and it identifies something 
different than a track of a video.

>
>
>>> Here, we chose @name to expose a given identifier for a track 
>>> inside
>>> multitrack media files or provide an identifier for external 
>>> tracks.
>>
>> For "inside" tracks this might be a simple string; Is @trackname 
>> taken?
>> probably "external" track (s?) might be a uri? so should have its 
>> own
>> attribute?
>>
>> In fact, why not include the @name attr in <video> and <audio> 
>> since @name
>> in other elements is associated with access by host DOM scripts?
>
> @trackname is possible, but I don't follow why @name should be a 
> problem.

Just because @name is already employed in the language for a different 
purpose?

>
>>> Consistency across the API made us chose this attribute name also 
>>> for the
>>> <track> element.
>>
>> Sorry if this is a late comment, but please let's look for 
>> consistency
>> across the api for all elements, especially, in this case, other 
>> embedded
>> elements
>
> The consistency that I am talking about is a consistency within the
> same element. I think that goes over consistency across different
> elements, even if they are elements of the same class.

OK, @name is already used in elements of the same class, if class 
means a category like embedded content.

> I have not seen
> a requirement anywhere for reusing attribute names across elements
> other than the global attributes linked to above.

Same requirements and best practice for all elements/attributes, I 
think. Are there other examples where the same string is used for 
attributes that carry different information?

Anne wrote > Elements using name="" are found using 
getElementsByName() which does not
look at whether name is used on an element where it is allowed or not.

Thanks, getElementsByName() has nothing to do with attributes named 
@name. That interface deals with element names, not atributte name.

>
> Regards,
> Silvia.

All in all, existing usage of @name in elements is not crystal clear 
except it appears @name can be used to access an iframe element or 
object by script. same or similar to @id. .

Best Regards,
Joe
Received on Monday, 12 April 2010 12:04:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:07 GMT