Comments | webdesign: Special Exceptions for Safari

cyclotron in webdesign

Special Exceptions for Safari

Aug 08, 2007 09:52

I know people swear up n down about CSS. But having used it exclusively for 10 months now, its a piece of crap. Only because every single browser needs special rules. I didnt need that with tables ... development time has more than doubled ( Read more... )

Leave a comment

Back to all threads

ninsun August 8 2007, 17:01:02 UTC

I have to agree with you. I just took a web design class and all we learned was CSS. I think tables are MUCH better.

to you and the OP kevinblanchard August 8 2007, 17:21:57 UTC

Since many of the browser makers haven't fully implemented CSS properly it can be an issue. That said, yes tables can be easier though it's considered bad coding. Though, every developer has to balance between integrity, quality and time. I do realize sometimes time is a big factor, and so sometimes you have to sacrifice things. I've been there before myself ( ... )

Re: to you and the OP cyclotron August 8 2007, 17:43:08 UTC

Considered bad coding by whom? Search engines? Most of these sites won't get more than 10 visitors a week due to the nature of the industry.

Re: to you and the OP kevinblanchard August 8 2007, 21:47:21 UTC

Not search engines. Poor coding as far as the standards put forth by the development community. It's not a solid line but certain things tend to be considered poor coding. To most web developers, using tables instead of CSS is like a programmer using GOTOs ( ... )

Re: to you and the OP cyclotron August 8 2007, 22:17:53 UTC

" put forth by the development community."

And who are they? Are you talking about popular opinion!? In technology?

CSS falls down on many issues. Take the whole Faux Column solution. Loading a graphic and requiring the screen to redraw it is better than few dozen bytes of HTML text?

The right place on the page is a search engine issue. Load time is a high traffic bandwidth issue.

How and the Hell is CSS "pure" when there are so many necessary hacks, work arounds and exceptions!? CSS driven sites dont even render the same on IE7 as on IE6. Nor on Opera. Nor on FF. You call that pure, I call that muddy - impure: confused.

Re: to you and the OP kevinblanchard August 8 2007, 22:38:55 UTC

"How and the Hell is CSS "pure" when there are so many necessary hacks, work arounds and exceptions!? CSS driven sites dont even render the same on IE7 as on IE6. Nor on Opera. Nor on FF. You call that pure, I call that muddy - impure: confused."By your description I see why you are confused. Those issues have zero to do with issues in CSS. Those "hacks" you refer to are from gaps and lack of support and proper implementation in the development of the browsers rendering engine, not in CSS. CSS is a web standard, like HTML. Not all browsers render both the i tag and the em tag. Is that an issue with HTML? No, it's an implementation issue on the browser. Same goes with CSS. The standards for CSS have already been defined. It's up to browsers to implement it fully and properly for it to work. As designers and developers we have seen this for years already with IE vs non-IE browser and code that *should* work with both doesn't and you have to tweak one or the other. It's not the HTML or JS usually it's the browsers and how it renders it ( ... )

Back to all threads