Ticket #72 (new feature)

Opened 7 years ago

Last modified 4 years ago

make the browser's back button interoperate with OL

Reported by: jrf Owned by: metacarta
Priority: major Milestone: Future
Component: general Version:
Keywords: Cc:
State:

Description (last modified by jrf) (diff)

If a user is looking at an OL map, then jumps to another page and then clicks the "back button" in their browser, the OL map appears to loose state. It sounds like there are several ways to fix this, including a hidden iframe, editing the browser history with js, rewriting the URL, and possibly more. Let's evaluate and do one of these.

Change History

Changed 7 years ago by euzuro

  • milestone Farallon Islands deleted

Changed 7 years ago by sderle

  • milestone set to 2.3 Release

Changed 6 years ago by sderle

  • owner set to sderle

Changed 6 years ago by euzuro

  • milestone changed from 2.3 Release to 2.4 Release

Changed 6 years ago by sderle

  • milestone changed from 2.4 Release to 2.5 Release

Changed 6 years ago by jrf

  • priority changed from major to blocker
  • description modified (diff)

Consider whether this sandbox work can help:

 http://trac.openlayers.org/browser/sandbox/elemoine/openlayers/lib/OpenLayers/Control/History.js

Changed 6 years ago by crschmidt

  • owner changed from sderle to metacarta
  • priority changed from blocker to major

Changed 6 years ago by fredj

Useful documentation:  http://dev2dev.bea.com/pub/a/2006/01/ajax-back-button.html

Changed 6 years ago by crschmidt

  • milestone changed from 2.5 Release to 2.6 Release

Bumped to 2.6 per IRC meeting

Changed 5 years ago by crschmidt

  • milestone changed from 2.6 Release to 2.7 Release

Changed 5 years ago by euzuro

  • milestone changed from 2.7 Release to 2.8 Release

Mass ticket move out of 2.7 in preparation for a release plan.

If you are actively working on this task, and think that you can help this ticket to get finished and closed by September 1, please move it back to 2.7.

Changed 4 years ago by crschmidt

  • milestone changed from 2.8 Release to 2.9 Release

See also #1347

Changed 4 years ago by crschmidt

  • milestone changed from 2.9 Release to Future

Release manager policy at this point:

  • 2.9 is for tickets which have existing work done on them, or bugs even if they don't.
  • Future is for tickets that no one has done any work on.

If at any time someone decides they are going to work on a ticket, they can pull a ticket back from Future to the current milestone, but putting a ticket in a milestone does not mean anything for its likely release unless it has code available.

Code which has patches ready for review should almost always go into the milestone for the next release.

Note: See TracTickets for help on using tickets.