[
https://issues.apache.org/jira/browse/MYFACES-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587862#action_12587862
]
Mario Ivankovits commented on MYFACES-1855:
-------------------------------------------
It would be really great if you could externalize the javascript too. Currently
it is simply inlined into the source, which looks not very professional I think.
> hidden fields created when using h:commandLink and f:param should be created
> and removed using javascript
> ---------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-1855
> URL: https://issues.apache.org/jira/browse/MYFACES-1855
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
>
> Myfaces render the hidden fields before the end of the form, which cause
> compatibility problems when someone does not use h:form to encapsulate a
> form. Mojarra or jsf ri does not, instead create the hidden fields before
> submit (including the hidden fields for params), submit the form an then
> remove the hidden fields to avoid unwanted effects. Myfaces set the hidden
> fields (if it is not rendered on the form creates it), submit the form and
> then set the values of the hidden fields to null.
> I have noted that autoscroll feature available when using tomahawk + myfaces
> uses oamSetHiddenInput instead render the hidden autoscroll part.
> After thinking a lot (A LOT!!) about this problem, the best for solve this
> problem is do not render hidden fields for this case, but let the code for
> hidden fields (compatibility with tomahawk, since jscookmenu use this
> feature, this should change in a future release). Instead, for h:commandLink,
> set and remove the hidden fields using javascript.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
