ENGAGE-230: Implement a means for bookmarking and history support of content within the Screen Navigator

Metadata

Source
ENGAGE-230
Type
New Feature
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Colin Clark
Reporter
Colin Clark
Created
2009-09-15T13:27:03.000-0400
Updated
2010-03-09T15:15:53.000-0500
Versions
N/A
Fixed Versions
  1. 0.3b
Component
  1. Screen Navigator

Description

At the moment, the Screen Navigator component provides a means for navigating between documents displayed on a phone. In order to provide seamless transitions between pages, we update the DOM via ajax instead of reloading the page. As a result, we break bookmarkability and history support.

Most AJAX apps have settled on a solution that uses URL fragments to support bookmarkability. While this isn't ideal, it should work quite nicely with a bit of help from the server-side.

Comments

  • Justin Obara commented 2010-02-26T11:09:22.000-0500

    Bug Parade Engage 0.3

  • Colin Clark commented 2010-03-09T15:00:03.000-0500

    I fixed this issue at r9574 with the inclusion of the jquery.hashchange plugin.