Sticky-less Hover

Safari version 1.2 has been released. In addition to all of the other new features, I’m happy to see that the “sticky hover” bug has been squashed.
Previously, some CSS hover states would stick on hovering. Oddly, if you moved the mouse away from the hover area up, the state would return to it’s normal appearance. But moving the mouse left, right or down would sometimes result in the hover getting stuck.
Anyhow, it seems to be fixed with the release of 1.2, which makes me smile. The navigation for this site works like a charm now in Safari 1.2 — as do the Accessible Image-Tab Rollovers I had whipped up for FC a while back.


  1. France says:

    I’m looking forward to confirming this fixes the aggressive cacheing bug suffers from in Safari. It downloads every CSS image, resulting in a painfully slow experience due to my extensive use of image replacement techniques.
    Background at
    If only the IE team had some guys like Dave Hyatt. He was very accomodating and essentially squashed the bug immediately. My hero.

  2. It’s a good upgrade. The only basic thing that annoys me about Safari right now is the handling of auto-complete in the address bar. It should go with the shortest match in the list, but it doesn’t. I have no idea how it determines the first match, but it certainly seems to lack logic. For example, if I start typing:
    You would expect it to complete to this:
    But nay. Instead, it would go to this:
    Even if the shorter URL is in my history. Does that make sense? Not much.
    I will digress no more. Always glad to see a Safari update.

  3. Olivier says:

    I think auto-complete in the address bar select the most recent or most visited URL instead of the shortest one. It’s convenient sometimes but annoying otherwise, I agree.

  4. nick says:

    I upgraded today and I still got the hover-bug, using li:hover to make the bullet disappear and reappear, no matter where the mouse went. Later I switched to just switching colors, which worked just fine. For the record.

  5. James says:

    Ok, ok, it’s a small point, but still no support for min-height. This is, without doubt, my major gripe with Safari…and it hasn’t been fixed. Does this drive anyone else mad? Has anyone found a workable fix?

  6. Shaun Inman says:

    Aw man, they fixed the @media ScReEn bug! I was using this to account for the fact that Safari doesn’t apply borders and padding to form elements. Now all of my form elements that have 1px border and 1px padding are coming up 4 pixels too short

  7. Colly says:

    Speaking of form elements, drop down menu css styles are suddenly taking effect in Safari 1.2. All the tinkering for the benefit of other browsers has appeared to shrink my drop down menus to child-size versions that may or may not be particularly ‘accessible’, but have been described as ‘cute’ by everyone in the office…

  8. tarun says:

    It actually annoys me how much stuff you have to tab through from the address bar to the page if you have your bookmarks bar available. Especially since the bookmarks bar has its own shortcuts.

  9. France says:

    Hmm, darn. Safari 1.2 available only for OS X 10.3.
    I totally understand Apple’s business decision here since they want everyone to buy 10.3. But you and I will be debugging against 1.0 and 1.2. The question becomes, “can you run multiple versions on 10.3?”

  10. Shaun Inman says:

    And the answer becomes “Not unless Dave can score us some stand-alone versions.” Since Safari is tied to the system version of WebCore a stand-alone would have to be hacked to run an isolated instance of an outdated WebCore. I don’t know if this is possible. Of course, we though the same about IE PC…
    The form linked in my previous post was fixed by removing the width of the containing element and floating it which forces it to synch up around its contents. I was able to remove the Safari hack all together. (Just don’t look at the source–tag soup–it had to display normally in NS 4.x because of the client’s constituency)

  11. France says:

    Well, I tried :) I renamed and packaged up the Safari 1.1 app, manually downloaded 1.2, installed it, placed the renamed 1.1 app elsewhere, opened 1.1, the About Safari listed it as 1.1… but 1.2′s new features were in there.
    Eh, well.

  12. Jayme says:

    I wish Safari 1.2 was as good as Firebird. But sadly it is not. Bummer.

  13. Actually, you could use the multiple Safaris. You’d have to get the old versions of the Web Kit, then you’d have to switch between them. It would be fairly easy to do. The only conflict I see is if new releases of Mac OS X have changed the interface between the system and Web Kit, but we’d have to see.
    I’d be willing to try it out and write it up if I could be provided with the older Safari installers (or copies of Web Kit and the app).

  14. Gambit says:

    Its always nice getting an upgrade to your most used piece of software. Im glad they brought back the old file icon with the download status bar on it from Os 9.
    Bit of a bummer for 10.2 people, its a little unfair that they cant use anything above Safari 1.0. I suppose that how it goes with software, if you want the latest in one you’ve gota have it in all.
    When designing I find that Safari is the easiest browser to work with, most css blunders still seem to pass, while IE5.5 mac, is the worst, css must be perfect. I suppose it good, keep one neat and correct.

  15. Printing is greatly improved in Safari 1.2.

  16. Gambit says:

    I just noticed it. When you drag imges from the browser to the desktop it does it instantly, they way mozilla does.
    Before it would connect and download the image with the download manager.