The Macintosh crowd is all abuzz about the new Apple web browser, called Safari. It’s apparently based on the KHTML rendering engine, and has a few bugs. The problem is, this makes Yet Another Browser that web designers have to worry about, because Safari has it’s own unique set of bugs different from other existing browsers. Mark Pilgrim asks should Safari be intentionally buggy?
My answer would have to be, “Yes. Temporarily.”
Since the Safari developers are actively listening to the community and working to fix the biggest deficiencies as quickly as possible, they should adopt a short-term strategy with a long-term goal. Introduce a Safari-specific method for hiding CSS from that browser for now. But with the understanding that they will work as hard as possible to make Safari fully compliant with the standards. Once that goal is reached, the bug is removed.
My suggestion for a bug:
/*\*/
this is hidden from safari
/* */
Related posts:
- IE7 to support standards?
" According to Eric Meyer, it seems that there is hope that Internet Explorer 7 may have improved standards support. He’s got a list of..." - FeedLounge wants browser developers
" The FeedLounge team is looking for some browser developers to help with testing. This is to help distinguish better between bugs that may be..." - How Bad Does Netscape 4 Suck?
" I’m on a mission, and I need your help. I want to collect links to essays about Netscape 4 suckage. I already have a..." - Choosing Standards
" There’s an old saying in the computing field: “The great thing about standards is that there are so many to choose from.” Funny, but..." - Weight Goal
" I was running late this morning, and in my rush to get ready for work, I forgot to weigh in. But based on my..."
One Comment
I think that’s a good idea. Maybe it will also help Konqueror along too.
Cheers,
BDKR