W3C home > Mailing lists > Public > public-html@w3.org > May 2007

Re: @role inheritance (nested tags) behavior, and a RFP

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Mon, 21 May 2007 20:11:10 +0100
Message-ID: <640dd5060705211211u21aff265u4d03a54019207e32@mail.gmail.com>
To: "Charles Ying" <charles.ying@gmail.com>
Cc: "HTML Working Group" <public-html@w3.org>


The role attribute was first proposed a number of years ago, and has
already been implemented in Firefox. The latest version of it is here
(a W3C Working Draft):


A quick Google will also yield a number of blog entries on the subject
(a few by me), as well as the Firefox references that I just referred



On 16/05/07, Charles Ying <charles.ying@gmail.com> wrote:
> Dear HTML WG,
> For those advocating a role= attribute (@role if you prefer), can you
> describe the behavior for inherited / nested tags? E.g., what does
> this mean?
> <p role="copyright">
>     Copyright &copy; 2007
>     <a href="http://www.pixverse.com/">PixVerse, Inc.</a>,
>     All Rights Reserved.
> </p>
> If it means what I think it means,
>    * It complicates a UA's ability to detect semantic content (it'll
> have to duplicate some CSS-like mechanism to properly follow this
> content.) Feedback from implementers is needed.
>    * This would advocate leveraging class= instead, since the nesting
> and inheritance mechanisms are already in place and authors would
> already be educated on class= 's behavior.
> I would also like to request that role= advocates draft a proposal to
> be available for reference and discussion.
> Best,
> Charles

  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Monday, 21 May 2007 19:11:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:21 UTC