[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812422#comment-13812422
]
Leonardo Uribe commented on MYFACES-3816:
-----------------------------------------
A flag disabled by default and activated by a web config param is valid, or a
new mode, which is the same.
The important thing for me is avoid changes that could cause problems and
incompatibilities later. In that sense, the spec is a straitjacket that we
cannot avoid.
I don't know why you insist so much to include it in the default mode and
change the spec semantic, more if the spec for this part was done allowing
multiple modes. See this line:
"... To accomadate the widest possible range of implementation choices to
support this feature, explicit names for modes other than "none" and "url" are
not specified. ..."
>From start, when it was done this feature, we already knew that "url" mode was
>not flawless, but we agreed to include it as the default mode because it was
>one known method that can be specified fully and is widely used, even with the
>pitfalls like the missing logic behind "open in new tab" or "missing url query
>string". Keep insisting in this issue is just continue with a discussion that
>was over long time ago. If you as an expert do not agree, you can expose your
>arguments at the EG level, I'm sure the change proposed is valid and probably
>it will be included in a further version of JSF but I have to be strict in the
>spec interpretation, more if I was one of the guys involved in the discussion
>of this feature. At least for me it was clear the agreement done.
> 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)
