[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812423#comment-13812423
]
Gerhard Petracek commented on MYFACES-3816:
-------------------------------------------
because it just leads to an useless std. mode and users can get issues with it
easily.
it might even look like a random behavior (since it depends on the interaction
before the refresh).
the only useful alternative is to log a clear warning at startup (in case of
the configured url-mode) that the url-mode is broken and a different mode
should be used.
i know - mark and i told ed about the url mode initially (even before the
eg-discussion started) and we also said that this use-case is important. the
known/accepted issues we talked about are about constellations with "open in
new tab".
> missing window-handling for initial requests
> --------------------------------------------
>
> Key: MYFACES-3816
> URL: https://issues.apache.org/jira/browse/MYFACES-3816
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-344
> Affects Versions: 2.2.0-beta
> Reporter: Gerhard Petracek
> Assignee: Leonardo Uribe
>
> for an initial request there is no window-id added to the url.
> (tested with 'url' for javax.faces.CLIENT_WINDOW_MODE)
> -> in case of a page refresh a new window-id will be created and it isn't
> possible to get back the original one. that can also happen with a
> page-refresh after multiple requests, if only ajax requests are used.
> that's a major issue for all scopes based on the window-id.
> it can be done with an initial redirect (default in codi) or js (with html5
> compliant browsers)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
