Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.2 Sprint 11
    • Component/s: Components/Renderers
    • Labels:
      None
    • Status Whiteboard:
      Hide

      size_large importance_medium

      Show
      size_large importance_medium

      Description

      Somehow we have never specified how web apps that have multiple simultaneous windows should operate. This issue requests to specify this behavior.

      1. 20120222-2138-i_spec_949.patch
        70 kB
        Ed Burns
      2. getWindowId.js
        4 kB
        werpu12

        Issue Links

          Activity

          Hide
          arjan tijms added a comment -

          An additional mechanism to store the window ID on the client that may be considered is the HTML 5 session storage. Like window.name, this is per-window/tab scoped.

          Some pointers:

          Show
          arjan tijms added a comment - An additional mechanism to store the window ID on the client that may be considered is the HTML 5 session storage . Like window.name , this is per-window/tab scoped. Some pointers: http://en.wikipedia.org/wiki/Web_storage#Local_and_session_storage http://balaarjunan.wordpress.com/2010/11/10/html5-session-storage-key-things-to-consider http://www.xul.fr/en/html5/sessionstorage.php (includes live demo)
          Hide
          gerhard_petracek added a comment -

          see also ClientSideWindowHandler in myfaces codi, however, that's a detail of an implementation.

          Show
          gerhard_petracek added a comment - see also ClientSideWindowHandler in myfaces codi, however, that's a detail of an implementation.
          Hide
          arjan tijms added a comment -

          Thanks Gerhard!

          For easy reference, here's the source of ClientSideWindowHandler.

          It's an implementation detail indeed and I hope it's okay to discuss it here, but doesn't windowhandler.html makes use of localStorage and not sessionStorage?

          Show
          arjan tijms added a comment - Thanks Gerhard! For easy reference, here's the source of ClientSideWindowHandler . It's an implementation detail indeed and I hope it's okay to discuss it here, but doesn't windowhandler.html makes use of localStorage and not sessionStorage ?
          Hide
          gerhard_petracek added a comment -

          you have to use what works across all browsers (which support html5) and with all constellations (get-/post-requests, open in new tab, window refresh,...)
          also myfaces core will use the approach we found for myfaces codi (at least the current prototype does).

          Show
          gerhard_petracek added a comment - you have to use what works across all browsers (which support html5) and with all constellations (get-/post-requests, open in new tab, window refresh,...) also myfaces core will use the approach we found for myfaces codi (at least the current prototype does).
          Hide
          Mark Struberg added a comment -

          Ed, Leo and I are currently working on the ClientWindow stuff. We now face the question if we really need to specify the name of the windowId URL parameter (ResponseStateManager#CLIENT_WINDOW_URL_PARAM). This is mostly a contract between the windowhandler javascript and the pluggable ClientWindow implementation which parses this parameter and extracts the windowId from it.

          The only part so far where we would need it is to 'rewrite' h:link and stuff via encodeActionUrl, encodeBookmarkableUrl, etc. But this could probably also be done in JavaScript on the client side. In this case we would not need to specify the windowId URL parameter in the spec at all. Both options of course have pros and cons!

          Show
          Mark Struberg added a comment - Ed, Leo and I are currently working on the ClientWindow stuff. We now face the question if we really need to specify the name of the windowId URL parameter (ResponseStateManager#CLIENT_WINDOW_URL_PARAM). This is mostly a contract between the windowhandler javascript and the pluggable ClientWindow implementation which parses this parameter and extracts the windowId from it. The only part so far where we would need it is to 'rewrite' h:link and stuff via encodeActionUrl, encodeBookmarkableUrl, etc. But this could probably also be done in JavaScript on the client side. In this case we would not need to specify the windowId URL parameter in the spec at all. Both options of course have pros and cons!

            People

            • Assignee:
              Ed Burns
              Reporter:
              Ed Burns
            • Votes:
              14 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 week, 1 day
                1w 1d
                Remaining:
                Time Spent - 6 hours, 45 minutes Remaining Estimate - 1 week, 17 hours, 15 minutes
                1w 17h 15m
                Logged:
                Time Spent - 6 hours, 45 minutes Remaining Estimate - 1 week, 17 hours, 15 minutes
                6h 45m