[
https://issues.apache.org/jira/browse/MYFACES-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved MYFACES-2768.
----------------------------------
Fix Version/s: 2.0.1-SNAPSHOT
Resolution: Fixed
The issue was a small refactoring bug I introduce while I cleaned up the j4fry
pps code.
I accidentally forgot to rename one of the old variables in a newly introduced
closure which was supposed
to take over the old code by utilizing our dom functionality.
> jsf.js internal myfaces parameters do not work anymore
> ------------------------------------------------------
>
> Key: MYFACES-2768
> URL: https://issues.apache.org/jira/browse/MYFACES-2768
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.1-SNAPSHOT
> Reporter: Werner Punz
> Priority: Minor
> Fix For: 2.0.1-SNAPSHOT
>
>
> The internal myfaces parameters have been broken by the refactoring:
> <h:commandButton id = "button1" value = "Increment left" action =
> "#{count.increment}" onclick = "jsf.ajax.request(this, event, {render:
> 'out1', execute: 'out1 button1',
> myfaces:{errorlevel:'ERROR', pps:true,
> queuesize:1}}); return false;" />
> fails while
> <h:commandButton id = "button1" value = "Increment left" action =
> "#{count.increment}" onclick = "jsf.ajax.request(this, event, {render:
> 'out1', execute: 'out1 button1'}); return false;" />
> This is not a showstopper since queue control and pps are not part of jsf 2.0
> but are preparation code for
> 2.1 so I can live with not having them currently enabled. The fixup either
> will go into 2.0.1 or 2.0.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
