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

Opening from doc search opens new window - clicking close returns to the portal in the new window

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.1.1
    • Fix Version/s: None
    • Component/s: User Interface
    • Epic Link:
    • Rice Module:
      KNS
    • Application Requirement:
      Rice
    • KAI Review Status:
      Review Completed

      Description

      This is going to (and has) confused users. The expectation of clicking the close button if a page has been opened in a new window is to close that window. The link is rendered by documentControls.tag. I'm not sure if the current implementation has any way of knowing that it was loaded from document search. But, if so, this link should probably check the opener and see if it should simply close the window instead of invoking the close action on the servlet.

        Attachments

          Activity

          Hide
          ewestfal Eric Westfall added a comment -

          This needs to be reviewed by KAI to verify that the functionality that Jonathan describes is desirable.

          Show
          ewestfal Eric Westfall added a comment - This needs to be reviewed by KAI to verify that the functionality that Jonathan describes is desirable.
          Hide
          ewestfal Eric Westfall added a comment -

          Reviewed in the KAI meeting today:

          https://wiki.kuali.org/display/KULRICE/September+2,+2010+meeting

          Decision was as follows:

          First of all, there are two contexts we are referring to here where a document is opened:

          1) A "pop-up" context
          2) A "same-window" context

          The pop-up context happens when a window gets popped up by clicking on a link, or when clicking on a document link in an email.

          For these cases the following decision was made: When the close button is clicked it should close the window/tab instead of returning to the portal

          For the same-window context, this is the case where someone clicks on a document from action list, document search, etc. and it opens in the same-window.

          For these cases, the following decision was made: When the close button is clicked it should return to the page it was on prior to the document being opened (this will usually be the action list or document search)

          In order to facilitate this, we may need to pass information to the document url that identifies the calling context (the kns would then decide what to do with this). Additionally, we will probably need to maintain some sort of "return stack" within the KNS session to determine where to return to when the document is closed...this could also be used to implement breadcrumbs at some point in the future

          Show
          ewestfal Eric Westfall added a comment - Reviewed in the KAI meeting today: https://wiki.kuali.org/display/KULRICE/September+2,+2010+meeting Decision was as follows: First of all, there are two contexts we are referring to here where a document is opened: 1) A "pop-up" context 2) A "same-window" context The pop-up context happens when a window gets popped up by clicking on a link, or when clicking on a document link in an email. For these cases the following decision was made: When the close button is clicked it should close the window/tab instead of returning to the portal For the same-window context, this is the case where someone clicks on a document from action list, document search, etc. and it opens in the same-window . For these cases, the following decision was made: When the close button is clicked it should return to the page it was on prior to the document being opened (this will usually be the action list or document search) In order to facilitate this, we may need to pass information to the document url that identifies the calling context (the kns would then decide what to do with this). Additionally, we will probably need to maintain some sort of "return stack" within the KNS session to determine where to return to when the document is closed...this could also be used to implement breadcrumbs at some point in the future
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.
          Hide
          ewestfal Eric Westfall added a comment -

          Closing as this may not be relevant with the newly redesigned document search, but logged the general functionality as described on this document https://docs.google.com/a/kuali.org/document/d/1hm-cgeUXwntSrIotTnV29KoqNajZ6TS4tCOcB66ZMkI/edit

          Show
          ewestfal Eric Westfall added a comment - Closing as this may not be relevant with the newly redesigned document search, but logged the general functionality as described on this document https://docs.google.com/a/kuali.org/document/d/1hm-cgeUXwntSrIotTnV29KoqNajZ6TS4tCOcB66ZMkI/edit

            People

            • Assignee:
              Unassigned
              Reporter:
              jkeller Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: