On 31 mar, 13:55, Ian Bambury <[email protected]> wrote:
>
> > If I'm correct, then you should probably pass down a "is default" flag
> > to setMenuByToken and only call History.newItem if !isDefault, i.e.
> > change your framework a bit...
>
> I don't need to. I already *know* when I need to use replace (the original
> token is blank), and the code already does what it should (and did before I
> posted) - the problem is, as originally stated in my first post, that...
>
> Window.Location.replace() doesn't work in Safari or Chrome or Opera
>
> and I'm looking for a fix or workaround.
Ah, OK, then just don't do anything if the original token is blank?
i.e. http://examples.roughian.com will show the exact same thing as
http://examples.roughian.com/#Home, just without showing #Home in the
URL. Or is this a problem?
(or have I totally misunderstood how your menus work?)
(note that on examples.roughian.com, I don't know if you're using
Window.Location.replace, but it creates a new history entry for #Home
in Firefox 3.0.8; and then after navigating a bit within the site,
when going back to the "blank token" with the back button, Firefox
doesn't seem to fire history listeners --or your code just does
nothing because it is already showing the #Home--, but when going back
once more --outsideexamples.roughian.com-- and then clicking next to
return back to examples.roughian.com, your onModuleLoad calls
Location.replace or History.newItem and deletes the "forward" history)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
