Comments on: Building the YUI Browser History Manager

By: kakrat

kakrat — Sat, 04 Sep 2010 09:59:36 +0000

Saving state to hidden field is an issue with dynamic pages. The value is always the value set by server when the page load.

By: Eric Miraglia

Eric Miraglia — Tue, 01 Jun 2010 21:49:02 +0000

@Riyaz — The best place to ask questions about YUI History (or any other YUI component) is on the forums: http://yuilibrary.com/forum/ . -Eric

By: Riyaz

Riyaz — Tue, 01 Jun 2010 20:45:49 +0000

Hi,
I’ve been trying to figure out how to use YUI history manager to “update” history rather than just “add” to it (eg: you delete a page, and you’d like to replace the url to point to the next valid page, so that clicking back shouldnt point to the deleted page).

Would anyone know if YUI history manager allows this? Thanks.

By: kakrat

kakrat — Thu, 11 Mar 2010 09:01:55 +0000

Is there any likelihood that the state returned by getCurrentState during initializatiobn be different from the the initial state registered at all?

Here is my thought about the state issue.
1. the state is fully determined by bookmark if there is a bookmark, so the current state is the state of bookmark.
2. the state returned by getCurrentState during startup is actually always the same as the registered state retrieved from bookmark, since
2.a. the hidden field _stateField’s value is always empty druing startup, since the browser will not set its the value to value set up by script, instead the browser set it to the value downloaded from server, so it’s always empty. if _stateField’s value is empty, then getCurrentState during startup return the state as is regitered initially.
2.b even if 2.a may not always be true, the value in statefield should corresponds to the bookmark, so the result returned by getCurrentState during startup is still the same as the state by bookmark.

If my thinking is correct, then I think your pattern of BHM samples should be re-examined.

By: Lanyon

Lanyon — Tue, 24 Mar 2009 05:55:31 +0000

Thanks so much! Because of the awesome B.H.M. script I was able to make my ajax truly functional. I can hardly wait to see the looks on the faces of other developers when I show them the site :)

By: Julien Lecomte

Julien Lecomte — Thu, 12 Feb 2009 19:48:08 +0000

@Ran

Unfortunately, you can’t prevent the state of the page to remain the same when the user clicks the navigation buttons.

- Julien

By: Ran

Ran — Thu, 12 Feb 2009 06:16:53 +0000

Hi Julien,

I have a quick question on the use of History Manager:

It seems that when the Back button is pressed, the manager updates the current state automatically. How do I go about implementing a validation callback so that when ‘back’ button is intercepted I can decide based on that callback’s returned value to block the operation and leave the app is the state it was prior to pressing ‘back’ button?

Thanks!
Ran

By: Javascript Front Controller for AJAX Applications | Jackson Miller

Javascript Front Controller for AJAX Applications | Jackson Miller — Thu, 03 Jul 2008 06:40:05 +0000

[...] YUI solution to the back button is much more complex than I initially thought (then I found this really great post about what it took to create it). Hopefully I didn’t think about that because it is late. Anyway, I don’t want to [...]

By: 갸릉갸릉-rediaSpace » Blog Archive » Ajax 뒤로가기 완전 해결 라이브러리-dsHistory

갸릉갸릉-rediaSpace » Blog Archive » Ajax 뒤로가기 완전 해결 라이브러리-dsHistory — Mon, 04 Feb 2008 09:29:18 +0000

[...] YUI Browser History Manager, Julien Lecomte [...]

By: » Presenting dsHistory: Another Way to Revisit the Past debugger;

» Presenting dsHistory: Another Way to Revisit the Past debugger; — Wed, 16 Jan 2008 03:36:31 +0000

[...] support. Since it’s still pretty new, I highly recommend you take a good look at Lecomte’s YUI post to see how he built it and understand the choices JS developers have right now as well as how he [...]