Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8876

Backbutton support for js actions (pushing history of js actions to browser history)

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2
    • Fix Version/s: 2.3
    • Component/s: Development, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Session
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      "e.g. preserve facet and pagination choices
      solution could be a simple as having a jQuery plugin that stores choices and reapplies those choices.

      Kamal: need an OnLeaveEvent that we can use to tack on some js functions that user has enacted so that it can be captured in the browsers history and viewed with a backbutton view."

        Attachments

          Issue Links

            Activity

            Hide
            masargen Matt Sargent added a comment -

            Backbutton changes for light box content - when a light box is opened from another the back button should take you back to the prior light box.

            Show
            masargen Matt Sargent added a comment - Backbutton changes for light box content - when a light box is opened from another the back button should take you back to the prior light box.
            Hide
            wwashington William Washington (Inactive) added a comment -

            Dev considerations:

            • Lightbox behavior - does it close the lightbox and take you back where you were?
            • Search results - every time a user hits a search button
              • some browsers already cache this for users anyway.
            • don't want to undo any actions

            Other options:

            • Push a component refresh to history.
              • Dev concern of how to rebuild page based on pop.
            Show
            wwashington William Washington (Inactive) added a comment - Dev considerations: Lightbox behavior - does it close the lightbox and take you back where you were? Search results - every time a user hits a search button some browsers already cache this for users anyway. don't want to undo any actions Other options: Push a component refresh to history. Dev concern of how to rebuild page based on pop.
            Hide
            wwashington William Washington (Inactive) added a comment - - edited

            I took a stab at which actions should be logged in the browser's history:

            Actions to support:

            • navigation actions (assumed to be included)
              • from page to page (back button navigates back to page)
              • from view to view (back button navigates back to view)
              • from page to lightbox (back button closes lightbox)
              • from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page)
              • [Secondary Requirement] from lightbox to subsequent lightboxes (back button navigates back to first lightbox)
            • search results
              • from search results to view (back button navigates back to search results)
              • from search results to new search results (back button navigates back to previous search results)

            No support needed:

            • reversing of actions taken
              • If page state has changed:
                • document is deleted (show error page)
                • KEW or other state change (show document with updated state, and with an info message, "This document has been updated since you last saw it")
                • data change (show document with updated state, and with an info message, "This document has been updated since you last saw it")
            • launching any type of dialog: lightbox, message box, popover, etc.
            • filters added to search results (this item is meant to note that a user shouldn't not be able to "unfilter" search results by hitting the back button. and even though this parameter isn't sent to the browsers history, when a user returns to a page that has filtering of search results via back button, it should be in the state that they left it.)

            Still needs definition/analysis:

            • Ability to define a component such that its refresh is added to the history
            Show
            wwashington William Washington (Inactive) added a comment - - edited I took a stab at which actions should be logged in the browser's history: Actions to support: navigation actions (assumed to be included) from page to page (back button navigates back to page) from view to view (back button navigates back to view) from page to lightbox (back button closes lightbox) from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page) [Secondary Requirement] from lightbox to subsequent lightboxes (back button navigates back to first lightbox) search results from search results to view (back button navigates back to search results) from search results to new search results (back button navigates back to previous search results) No support needed: reversing of actions taken If page state has changed: document is deleted (show error page) KEW or other state change (show document with updated state, and with an info message, "This document has been updated since you last saw it") data change (show document with updated state, and with an info message, "This document has been updated since you last saw it") launching any type of dialog: lightbox, message box, popover, etc. filters added to search results (this item is meant to note that a user shouldn't not be able to "unfilter" search results by hitting the back button. and even though this parameter isn't sent to the browsers history, when a user returns to a page that has filtering of search results via back button, it should be in the state that they left it.) Still needs definition/analysis: Ability to define a component such that its refresh is added to the history
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            According to Brian, all these items remain:

            • from page to lightbox (back button closes lightbox)
            • from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page)

            And we need to verify that these items are working. He thinks they should.

            • from search results to view (back button navigates back to search results)
            • from search results to new search results (back button navigates back to previous search results)
            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - According to Brian, all these items remain: from page to lightbox (back button closes lightbox) from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page) And we need to verify that these items are working. He thinks they should. from search results to view (back button navigates back to search results) from search results to new search results (back button navigates back to previous search results)
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            I can verify the two last items because they was taken care of as part of the session work:

            from search results to view (back button navigates back to search results)
            from search results to new search results (back button navigates back to previous search results)

            Show
            jkneal Jerry Neal (Inactive) added a comment - I can verify the two last items because they was taken care of as part of the session work: from search results to view (back button navigates back to search results) from search results to new search results (back button navigates back to previous search results)
            Hide
            wwashington William Washington (Inactive) added a comment -
            • "from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page)"
              Brian notes that this scenario isn't supported by KRAD, and therefore we needn't support it in the back button support.
            • "from page to lightbox (back button closes lightbox)"
              This item still needs to be addressed before we can close the jira.
            Show
            wwashington William Washington (Inactive) added a comment - "from lightbox to page (back button doesn't reopen lightbox, but navigates back to parent page)" Brian notes that this scenario isn't supported by KRAD, and therefore we needn't support it in the back button support. "from page to lightbox (back button closes lightbox)" This item still needs to be addressed before we can close the jira.
            Hide
            bsmith Brian Smith (Inactive) added a comment -

            Added back button close for the lightbox, but found other issues with the history getting messed up after a lightbox closes (unrelated)

            Show
            bsmith Brian Smith (Inactive) added a comment - Added back button close for the lightbox, but found other issues with the history getting messed up after a lightbox closes (unrelated)

              People

              • Assignee:
                bsmith Brian Smith (Inactive)
                Reporter:
                wwashington William Washington (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: