Comments on: Is CSS 3 over-baked?

By: Brian Shapiro

Brian Shapiro — Fri, 23 Oct 2009 19:01:50 +0000

Rather than a multi-column module, I’d prefer an overflow attribute that allows me to have the overflow of one element redirect to another element. Strict columns are unnecessarily arbitrary from a designers perspective.

By: Gravitational

Gravitational — Wed, 23 Sep 2009 08:10:35 +0000

Replace ‘please’ with ‘people’ twice on comment 16. Strange!

By: Gravitational

Gravitational — Wed, 23 Sep 2009 08:06:22 +0000

Yes its true there is more talk more people talking about it and more noise (it hurts).

But also consider there are more people using the internet than ever before there are more please able to access the internet than ever before and there are more please owning computers/internet accessible devices than ever before!

By: Ollie

Ollie — Wed, 26 Aug 2009 10:39:35 +0000

True, true. Guess it can’t be perfect. :/

By: Peter Gasston

Peter Gasston — Wed, 26 Aug 2009 09:25:24 +0000

@Ollie: There’s currently a flash when using @font-face in Safari too, as they also wait for the font to load before applying it to the page. Firefox’s implementation differs, as they load unstyled text before applying the font.

By: Frederick Townes

Frederick Townes — Wed, 26 Aug 2009 08:22:27 +0000

There you go. AFAICS, the juice has to be worth the squeeze and there are numerous uses for things like this (your case reminds me of sifr for example), that make it worth it. And the debate continues. :)

By: Ollie

Ollie — Wed, 26 Aug 2009 06:39:42 +0000

@Frederic: I just came across this screencast http://css-tricks.com/video-screencasts/69-first-ten-minutes-with-typekit/ showing typekit, which uses javascript and @font-face to replace certain text. It is a really neat thing, but here show up two unpleasant things: It flashes because it waits until DOM is ready. One solution is to leave it, the other is to hide it with css visibility. Turn off JS and we’re screwed. And here’s the question again, when do we want to use it? :)

By: Alex

Alex — Sun, 23 Aug 2009 16:08:33 +0000

I think there are issues with offloading styling to JS, even if it’s just a simple check.

The Modernizr site has a tutorial with a bit of CSS code that only applies a gradient (WebKit property only) if the script sets a certain class on the body element. But the browser will already apply the gradient only if it supports it, all the code does is stop the gradient showing in browsers without JS enabled.

It seems to me to be duplicating the functionality already in CSS and moving it into JS. And it bloats the CSS file, you’re already specifying the background twice, but now in 2 separate rules, if you keep it in one rule with the non-webkit/non-moz property first then you’ll achieve the same effect with less CSS markup and no reliance on JS.

By: Frederick Townes

Frederick Townes — Fri, 21 Aug 2009 10:13:17 +0000

@Ollie, exactly!

By: Ollie

Ollie — Fri, 21 Aug 2009 10:11:32 +0000

@Frederick: I guess it depends on what kind of a project it is. Sometimes you can pimp it all up, sometimes you have to stick to the rules. :)