Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-11331

Better support for multi-tab navigation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.7.2
    • Component/s: Seam / JSF UI

      Description

      The problem
      JSF Backoffice UI depends on Seam Conversation context.
      Conversation ID is transmited via URL in REST links and is associated with sever side state (currentDocument, current selection ...).

      As a result, when using several tabs, if they all point to the same conversation, all the tabs share the same server side state, and this becomes a mess.

      The solution
      There is no simple way to detect that a user choose to navigate in a new tab.

      But Florent found the solution : we detect 'normal' navigation and add propagation of the conversation to the url.
      In all other cases, we use the default url that should not integrate the conversationId.

      <A href="nuxeo/somepage.faces" onclick="if(!event.ctrlKey){this.href='nuxeo/somepage.faces?converstaionId=0NXMAIN1'}"> Some doc </A>
      

      Integration
      This can be directly integrated inside RestDocumentLinkRenderer and RestDocumentLink.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                grenard Guillaume Renard
                Reporter:
                tdelprat Thierry Delprat
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: