There seems to be some debate on whether certain CSS "bugs" should be left in Safari. Of course this would be so that there are certain ways to hide CSS from Safari if someone wanted to. There are various methods that happen to work right now, and the thought is that leaving these bugs in the browser will help web developers.

I'd like to say that it won't. A lot of the current CSS "hacks" are used for specific things. The Simplified Box Model Hack for example is great for, fixing the flawed box model of IE5/PC, since it's one of the few browsers out there that is tripped up by this hack. Since Safari is also tripped up by it, it makes the entire hack useless.

In fact after a few back and forth emails with Safari developer Dave Hyatt, he agrees with me, and would like to fix the bug before the final version comes out. I hope this does indeed happen, as it would sure save me a lot of time (as well as others) in re-coding sites to work in Safari (and make Safari actually work the way it's supposed to).

IMHO, all the CSS parsing bugs should be fixed. I understand wanting to hide certain things from Safari (or to only show certain things in Safari) but I think if you want this you should add some Safari-only codes into the browser. Some may cringe at that notion and think of all the proprietary stuff in IE, but remember that Mozilla also has a few proprietary tags as well.

It could be something as simple as "safari-hide" and "safari-show" somewhere in the CSS (as comments, or tags, whatever). To me this is a much better solution because you're not introducing actual bugs into the browser, but instead are writing your own additions to the browser to make it easier for developers. You're also not then tied to a specific "hack" that could totally backfire on you when a new browser comes out and screws up the hack model (see above).

In the end however, the most important part is fixing ALL the bugs, rendering and otherwise, so that we never have to rely on "hacks" or proprietary code in the first place!