Vaska schrieb:
> With a very small change in the source code and the use of an
> undocumented function ( history(); ) in Klaus' script, I am able to
> have custom #hash values as they are represented in my href and use
> my own call to Ajax...the history mechanism seems to work perfectly...
>
> I simply adjusted line 230 from...to...
>
> //var hash = '#remote-' + (i + 1);
> var hash = uri;
>
> (probably not the most elegant solution, but this was the quick 2 min
> hack)
>
> 'uri' was already for my ajax call...
>
> NOTE: USE SAFARI 2.0.4 OR GREATER! ;)
>
> Thanks Klaus...
I have just committed and uploaded an enhancement, so that you can now
specify the hash prefix:
$('a.remote').remote('#output', {hashPrefix: 'chapter'});
will result in links with an hash like '#chapter1', '#chapter2' and so on.
See SVN or here:
http://stilbuero.de/jquery/history/
Yes, that Safari thing. Safari needs the hash to be updated after the
Ajax call is completed. This is build into jQuery.fn.remote but not into
jQuery.fn.history (which is a yet undocumented function I was using for
Tabs).
-- Klaus
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
