This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16323 - wouldn't it be beneficial to fire popstate (or another event) when the user browses to a new url, not just to session history entries?
Summary: wouldn't it be beneficial to fire popstate (or another event) when the user b...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-12 15:03 UTC by contributor
Modified: 2012-11-25 04:46 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2012-03-12 15:03:43 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#event-popstate
Complete: http://www.whatwg.org/c#event-popstate

Comment:
wouldn't it be beneficial to fire popstate (or another event) when the user
browses to a new url, not just to session history entries?

Posted from: 194.200.65.239
User agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Comment 1 contributor 2012-07-18 17:14:14 UTC 
This bug was cloned to create bug 18088 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-09-18 23:01:55 UTC 
Can you elaborate? A number of events fire in that kind of situation. What exactly is your use case?