Why this blog doesn’t decently render in Chrome

UPDATEVinny sent me a script that fixes it.  Much thanks!

Right after I wrote a neato article on Chrome and Google Bookmarks, my blog stopped “working” in Chrome.  I finally figured out why.

Apparently, the script set that powers my dropdown menu—the “Accessible Website Dropdown Menu”—is written to look for the string “Apple Computer” in a browser’s useragent and serve webkit-oriented stuff to those browsers.  But Chrome now lists “Google inc.” in the user agent.

More details are in the bug report I filed (which, rightly, was marked “works as intended,” since it’s a script problem, not a Chrome bug).

If any folks more adept at JS than I am want to either help me fix this or—better yet—help the UDM folks fix it, that’d be super :-D.

13 comments

  1. Gah! Thanks for the info Dani (and others who have recently mentioned this to me as well).  I will try to figure out why the menu is now not working in Opera [sigh].

  2. I’m not an early adopter – I like to wait a bit when something new comes out and people have a chance to identify any bugs that need to be fixed.

    I just embraced Firefox last year and am happy with it. I guess I need a good reason to switch to Chrome. Any thoughts?

  3. I am called by Bladam by someone.

    it was a derivative of Black Adam

    I am not black though, I am white.
    inside joke type thing Some say it reminds them of bladder

Leave a comment

Your email address will not be published.