This is my personal blog. The views expressed on these pages are mine alone and not those of my employer.

Wednesday, June 07, 2006

Ajax History Support in Safari Possible?

I got a great email from David Bloom today. He says that he has figured out a way to have fragment identifier history in Safari. I haven't gotten a chance to test this myself, since I don't have a Mac, but I'd love to hear folks experiences with it. His email:

"I figured out how to get fragment identifier history to work in Safari...

http://bloomd.home.mchsi.com/histapi/test.html (only works in Safari, tested on version 2.0.3)

It's unoptimized and there are still plenty of ways to make it "mess up", but what matters is that it is a working implementation of back/forward history in Safari with fragment identifiers :-). I think that the flaws (such as forgetting - but still keeping entries in the browser's history for - all but the most recent history state when you leave the site then click Back until you're at it) can be fixed using cookies, cached forms, or something like that."
// posted by Brad GNUberg @ Wednesday, June 07, 2006
Comments:
This crashed my browser when I entered a second value.

Also: Kevin Newman has had working safari back button going for a few weeks - check out:

http://www.unfocus.com/projects/HistoryKeeper/
# posted by Blogger Geoff Stearns : 9:11 AM
This post has been removed by a blog administrator.
# posted by Blogger david bloom : 10:33 AM
Update
I've got the leave-the-page-then-come-back bug corrected, as well as several other little quirks.
http://bloomd.home.mchsi.com/histapi/test.html

Geoff: what version of Safari and MacOS X are you running?
# posted by Blogger david bloom : 6:28 PM
It works on Safari 2.0.3 quite well, can go back and forward most of the time without a problem.

As is usual with Safari & Javascript like this though, if you get carried away and click too fast it does lock the browser up - it did the first time i tried it. There is obviously something not too Safari friendly going on it there, try logging whats happening using window.console.log() - would be able to tell what it crashes on then.
# posted by Blogger n : 8:13 AM
I tested it in Bon Echo 2.0a3 on Windows and it worked without any issues. This is some really neat stuff. Going to have to look deeper into how this actually work.
# posted by Blogger Neo Geek : 4:53 AM
This is sooooo beyond me, it is funny! I wish I knew as much as you do, and San Francisco rocks!
# posted by Blogger Jane Lake : 8:02 AM
Post a Comment

Links to this post: See links to this post
<$blogbacklinktitle$>
<$blogbacklinksnippet$>
<$i18npostedbybacklinkauthor$> @ <$blogbacklinkdatetime$>


<< Home

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]

AltStyle によって変換されたページ (->オリジナル) /