Dave Hyatt on the Safari team is looking for a top ten list of Safari problems in a limited area via Trackback (a way of tracing links to a blog post on the inbound side).

In no particular order:

1. Broken frame linking: Left frame has links that target a center frame. After a few clicks, links in the center frame die (no hand, no loading); links in the left frame can trigger (hand appears over links) but nothing happens.

2. Repeated entry, no storage, of HTTP Auth entries for sites with password protection. Revisiting a page in a new Safari session (after reboot or quitting and running Safari) requires re-entry of user name/password.

3. Non-conforming cookie behavior for international sites. Safari assumes that my site isbn.nu is not a legal second-level domain. International sites are restricted to third-level domains. That is you can set a cookie for blank.com, or blank.co.uk, but not blank.nu, which is a legal domain name. Hard to solve that one. Other browsers are more liberal, though. So you can't set .co.uk, but you can set isbn.nu.

4. Switching between tabs with an insertion point in a text field can cause the text field to be selected on its return, making it easy to delete an entry.

5. No Undo for deleting or retyping in field entries. (No other browser does that I know of, but why not Safari?)

6. No import/export of passwords, cookies, etc. across browsers. Why not add to iSync portfolio? Why not allow encrypted export using system admin password for access (messaging, whatever, to encrypt)

7. Proxy bug: when asked for proxy username/password over SSH forwarded port (127.0.0.1:80 -> remote port:8001), I can't check save password without a crash. I must enter each time and then it works fine.

8. FedEx and UPS sites don't print their images correctly: I can't figure this one out, but the lading bills that you can generate via the FedEx and UPS site to print and paste on boxes and documents print at 50 percent of their size on multiple computers of mine on multiple printers. From Internet Explorer 5.2.x, these same images print fine.

No offense friend, but none of your entries are about Safari rendering problems which is what David was referring to.

Well, it is unrealistic to expect people not to comment on issues that are related.

Bug #5 above - the lack of Undo in text fields - is particularly galling considering all the stuff about Undo in Apple's Aqua Human Interface Guidelines.

Even if I was a rendering programmer, I would still be asking the UI team what on earth they were up to.

Camino has undo in text fields.

The reason you don't have undo/redo in text fields is because Cocoa doesn't make it easy to do. In Cocoa's opinion, nothing important happens in a text field until after you leave it - so why bother to have undo/redo?