W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

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

From: Brian Kardell <bkardell@gmail.com>
Date: Tue, 21 Aug 2012 16:30:03 -0400
Message-ID: <CADC=+jcuqQOQs3fmEHiEpM+Tdd+4ETooSvks_xBBwmSV_pqfsg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: public-webapps <public-webapps@w3.org>, Ojan Vafai <ojan@chromium.org>
On Aug 21, 2012 4:03 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
> On Tue, Aug 21, 2012 at 12:37 PM, Ojan Vafai <ojan@chromium.org> wrote:
> > Meh. I think this loses most of the "CSS is so much more convenient"
> > benefits. It's mainly the fact that you don't have to worry about
> > the nodes exist yet that makes CSS more convenient.
> Note that this benefit is preserved.  Moving or inserting an element
> in the DOM should apply CAS to it.
> The only thing we're really losing in the dynamic-ness is that other
> types of mutations to the DOM don't change what CAS does, and some of
> the dynamic selectors like :hover don't do anything.

So if I had a selector .foo .bar and then some script inserted a .bar
inside a .foo - that would work... but if I added a .bar class to some
existing child of .foo it would not...is that right?

> > That said, I share your worry that having this be dynamic would slow
> > DOM modification too much.
> >
> > What if we only allowed a restricted set of selectors and made these
> > dynamic instead? Simple, non-pseudo selectors have information that is
> > local to the node itself (e.g. can be applied before the node is in the
> > DOM). Maybe even just restrict it to IDs and classes. I think that would
> > meet the majority use-case much better.
> I think that being able to use complex selectors is a sufficiently
> large use-case that we should keep it.
> > Alternately, what if these applied the attributes asynchronously (e.g.
> > before style resolution)?
> Can you elaborate?
> ~TJ
Received on Tuesday, 21 August 2012 20:30:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:38 UTC