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: Anne van Kesteren <annevk@opera.com>
Date: Mon, 12 Apr 2010 14:10:13 +0200
To: "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>, "Joe D Williams" <joedwil@earthlink.net>
Cc: "Sean Hayes" <Sean.Hayes@microsoft.com>, public-html <public-html@w3.org>
Message-ID: <op.va1tfblf64w2qv@annevk-t60>
On Mon, 12 Apr 2010 14:03:29 +0200, Joe D Williams <joedwil@earthlink.net>  
> 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?

Yes, e.g. the type="" attribute on <input> versus how it is used on <link>.

> 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.

That is getElementsByTagName(), not getElementsByName().

Anne van Kesteren
Received on Monday, 12 April 2010 12:11:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:01 UTC