- From: Jeffrey Way <jeffrey@envato.com>
- Date: Tue, 3 Jan 2012 19:22:58 -0500
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "Nicholas C. Zakas" <standards@nczconsulting.com>, www-style@w3.org
Received on Wednesday, 4 January 2012 00:23:26 UTC
Good point - not a huge difference. Still, I'd imagine that, given the choice, most would prefer the HTML class route for simple projects. But yeah - definitely not arguing against adding this. :) Jeffrey On Tue, Jan 3, 2012 at 7:15 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Tue, Jan 3, 2012 at 4:10 PM, Jeffrey Way <jeffrey@envato.com> wrote: > > For simple projects, there's a lot to be said for the readability of > > sticking with class-based detection, and doing: > > > > .someJSDependentTickerThingy { ... } > > .no-js .someJSDependentTickerThingy { display: none; } > > > > as opposed to either declaring multiple media query sections, or > abstracting > > all of it to the bottom...which can sometimes be confusing. But, for > heavier > > applications, this would be a huge help. +1. > > I don't think it's a big deal to have something like: > > .someJSDependentTickerThingy { ... } > @media (no-script) { .someJSDependentTickerThingy { display: none; } } > > ~TJ >
Received on Wednesday, 4 January 2012 00:23:26 UTC