4 ms·
> with the usual exception of Internet Explorer. Which, of course, makes it's entirely useless for real work. CSS properties for layouts that web developers c
by wvenable 16y ago
> with the usual exception of Internet Explorer.
Which, of course, makes it's entirely useless for real work. CSS properties for layouts that web developers commonly did in the 90's should have been in the spec from day one. Instead, CSS was far too concerned with word processor-like document layout than anything resembling a web page.
- lwhi 16y agohttp://dowebsitesneedtolookexactlythesameineverybrowser.com/ http://dowebsitesneedtolookexactlythesameineverybrowser.com/ EDIT: for the down-voting, disbeliever[1] ;) [1] http://en.wikipedia.org/wiki/Progressive_enhancement http://en.wikipedia.org/wiki/Progressive_enhancement
- wvenable 16y agoProgressive enhancement is fine for things like rounded corners but we're talking about multi-column support in CSS3. Rendered in IE9 your page will look it belongs to 1994.
- lwhi 16y agoI don't agree .. not many sites use multiple columns at the moment, and they can still look reasonably good (current). If not having multiple columns is a deal-breaker for a user, they'll switch browsers (which might not be such a bad thing). My point is, the fact that some browsers haven't implemented some features yet shouldn't be problem. A website usually doesn't need to look exactly the same on every browser - and following a system of progressive enhancement allows a developer to use newer features more openly.