W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

Re: Proposal for "Cascading Attribute Sheets" - like CSS, but for attributes!

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 5 Oct 2012 08:52:02 -0700
Message-ID: <CAAWBYDA3wt98Qw-mJzfdu3Q1jSA96JcuEHsL-hTm-QzJ_56_fA@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: public-webapps <public-webapps@w3.org>
On Fri, Oct 5, 2012 at 4:22 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
> On Tue, Aug 21, 2012 at 9:17 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> Similarly, some of the a11y folks have recently been talking about
>> applying aria-* attributes via CSS, again, because it's just so much
>> more convenient.
> What's the rationale for this radical change of mind? Back when ARIA
> was introduced, the a11y wanted to specifically avoid the introduction
> of reflecting DOM properties for the ARIA attributes in order to force
> authors to use setAttribute() so that JAWS could retrieve the ARIA
> data via COM in ARIA-unaware legacy IE.
> If the a11y folks were so serious about being compatible with IE7 a
> few years ago, why isn't there now similar concern that applying ARIA
> by a new mechanism would leave behind IE10 and earlier, which,
> presumably, currently have the same sort of expected enterprise
> lifespan as IE7 had when aria was introduced?

I have no idea.  However, it seems irrelevant for my proposal - as
currently specified, CAS desugars into setAttribute calls.

Received on Friday, 5 October 2012 15:52:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:49 UTC