436 words
David Hyatt bravely asks for input on the most-loved problems with Safari's rendering engine. I have some additional comments to make, but let's do the business first:
That said, I have to add that there are more sites which break on Safari than on the 'big' browsers – particularly in the JavaScript department. While I tend to consider that bugs of the site, rather than the browser, it is quite annoying to have to use another browser just fool some stupid web site into doing what it's supposed to do.
To finish, let me add that while I appreciate David's effort and obviously use it, I am a bit confused by the ways in which feedback for Safari can be left: The bug menu item in the program itself, Apple's bug reporter and occasionally with Dave. That's not entirely satisfactory – particularly as it isn't clear to which degree those reports are read and which problems Apple are aware of. Thus it is very hard to find a good balance when trying to figure out whether it is worth to submit a bug and how much time should be put into the bug report. [That's a general problem with Apple's responsiveness, not a Safari specific one.]
Also, it would be very helpful if there were a manual trackback entry field for the post, considering that far from all people use software that is capable of generating trackback pings as John Gruber pointed out.