location.href = and history.replace().
Others: thoughts?
Nathan
On Aug 5, 2009, at 4:58 AM, Mike Wilson wrote:
Nathan Hammond wrote:
I should have stated this one with a goal: the ability
to ensure that the popstate event always fires with a
full understanding of the (app/page) state when
navigating
wrote:
On Wed, 29 Jul 2009, Nathan Hammond wrote:
Possible Action Items
1. Specify the order in which history related events are triggered.
In what order would one expect the events triggered by
window.history.pushState({}, Title, #newhash)?
No events are triggered by doing that.
With my new
Hey Jonas et al.:
Thanks for the reply, forgive my disbelief on Clarification 1. :) If
I'm completely with you, that is entirely unexpected on my part (and
I've read this part of the spec a few times). Is this to imply that,
no matter what the arguments to pushState(), if the path is
? Is that defined
clearly?
Otherwise, this can be used during phishing attacks.
Sebastian
On Thu, Jul 30, 2009 at 4:13 PM, Nathan Hammond nat...@nathanhammond.com
wrote:
Hey Jonas et al.:
Thanks for the reply, forgive my disbelief on Clarification 1. :) If
I'm completely with you
Ian et al.:
About a year ago, after I wrote the first version of my history
manager, I began the process of looking into the HTML5 history spec
and had a few conversations with folks like Bertrand Le Roy, Brad
Neuberg, and Brian Dillard. Some of my notes from back then have been
