[
https://issues.apache.org/jira/browse/DELTASPIKE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko updated DELTASPIKE-939:
-----------------------------------------
Fix Version/s: 1.4.2
> dswid=tempWindowId for every duplicated tab in Chrome/Firefox
> -------------------------------------------------------------
>
> Key: DELTASPIKE-939
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-939
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.4.1
> Environment: Chrome 43.0.2357.125 (64-bit)
> Firefox 38.0.5
> Fedora 22
> Reporter: Sean Flanigan
> Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> I am using ClientWindowRenderMode.CLIENTWINDOW and a JSF page with
> <ds:windowId/>, and a ViewAccessScoped action bean which prints its identity
> whenever its corresponding commandButton is clicked.
> If I navigate via that button, or h:link, or <a href>, everything works
> as I expect: the dswid is preserved, and the bean has the same identity
> within the same browser tab. And if I use middle-click to open a new
> tab, each tab gets a new identity (new dswid) and a new instance of the
> bean.
> The problem happens when I use Chrome's "Duplicate Tab" feature, or Firefox's
> clone tab feature (drag and drop a tab while holding Ctrl).
> Whenever I clone a tab that way, I get (after a redirect) a new tab with
> dswid=tempWindowId, and each of these tabs is sharing the same instance
> of my ViewAccessScoped bean.
> You can see the same problem in the JSF playground, by visiting
> http://localhost:8080/ds/views/scope/viewaccess/test1.xhtml, cloning the tab
> twice and observing that dswid=tempWindowId in both clones.
> I think duplicated tabs should get their own identities, instead of
> sharing "tempWindowId".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
