You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/05/09 04:52:48 UTC
[jira] Commented: (MYFACES-2687) Make sure jsf.js is included if
client behaviors are rendered
[ https://issues.apache.org/jira/browse/MYFACES-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865528#action_12865528 ]
Leonardo Uribe commented on MYFACES-2687:
-----------------------------------------
Added proposed patch. An email was sent to dev list. If no objections I'll commit this code soon.
> Make sure jsf.js is included if client behaviors are rendered
> -------------------------------------------------------------
>
> Key: MYFACES-2687
> URL: https://issues.apache.org/jira/browse/MYFACES-2687
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-314
> Affects Versions: 2.0.0
> Reporter: Jakob Korherr
> Assignee: Leonardo Uribe
> Attachments: MYFACES-2687-core.patch, MYFACES-2687-shared.patch
>
>
> When attaching a ClientBehavior ( != <f:ajax>) to e.g. a <h:commandButton>, jsf.util.chain() is implicitly used by the <h:commandButton> when rendering the ClientBehavior.
> However if no <f:ajax> stuff is on the current page or jsf.js is not included manually by <h:outputScript library="javax.faces" name="jsf.js" />, we will get a JavaScript error saying "jsf is not defined", because jsf.util.chain() is used, but jsf.js is not there!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.