You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Struberg (JIRA)" <de...@myfaces.apache.org> on 2012/05/16 13:17:02 UTC
[jira] [Created] (EXTCDI-291) [CSWH] add UserAgent hook to
ClientConfig
Mark Struberg created EXTCDI-291:
------------------------------------
Summary: [CSWH] add UserAgent hook to ClientConfig
Key: EXTCDI-291
URL: https://issues.apache.org/jira/browse/EXTCDI-291
Project: MyFaces CODI
Issue Type: Improvement
Components: JEE-JSF20-Module
Affects Versions: 1.0.5
Reporter: Mark Struberg
Assignee: Mark Struberg
The decision to render ClientSideWindowHandlers intermediate page is often based on the current UserAgent.
It should be easier to overwrite the ClientConfig and plug in an own detection algorithm.
In our project we e.g. do not use blacklisting but whitelisting (explicitely enable the intermediate page for known browsers via regexp)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (EXTCDI-291) [CSWH] add UserAgent hook to
ClientConfig
Posted by "Mark Struberg (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTCDI-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg resolved EXTCDI-291.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.6
> [CSWH] add UserAgent hook to ClientConfig
> -----------------------------------------
>
> Key: EXTCDI-291
> URL: https://issues.apache.org/jira/browse/EXTCDI-291
> Project: MyFaces CODI
> Issue Type: Improvement
> Components: JEE-JSF20-Module
> Affects Versions: 1.0.5
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.0.6
>
>
> The decision to render ClientSideWindowHandlers intermediate page is often based on the current UserAgent.
> It should be easier to overwrite the ClientConfig and plug in an own detection algorithm.
> In our project we e.g. do not use blacklisting but whitelisting (explicitely enable the intermediate page for known browsers via regexp)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira