3 ms·

Do you actually develop sites with this kind of thinking? I'm shocked that you'd rather use a 1px png (adding an additional http request) and JavaScript to achi

Do you actually develop sites with this kind of thinking? I'm shocked that you'd rather use a 1px png (adding an additional http request) and JavaScript to achieve an effect that CSS can handle all on its own. We use browser extensions because specs like CSS3 aren't suddenly turned on one day like a light switch. You can make your layout look nicer on cutting-edge browsers and by the time the old browsers are no longer around and the spec is in widespread use you can remove the extensions. It's trivial to remove CSS from a stylesheet. It's usually a pain in the ass to re-implement CSS functionality from 1px pngs and JavaScript hacks once all the browsers have caught up.

metamemetics 16y ago
>CSS can handle all on its own CSS can't handle it all on its own is the point. And yes I'd rather incur the extra bandwidth of a 1px wide crushed PNG in order to have simpler code and have my site support all-browsers, including ones whose team made good CSS a priority before other browsers did. Rewarding the large monoliths by coding specifically for them simply because of their popularity while punishing teams that actually prioritized CSS is what got us into this mess in the first place. Would you encourage this behavior pre-CSS4? pre-CSS5?