[
https://issues.apache.org/jira/browse/TRINIDAD-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626495#action_12626495
]
Stephen Friedrich commented on TRINIDAD-1198:
---------------------------------------------
Ah, sorry, JSF is in fact tricky.
Exactly because the input fields value is not processed it stays empty on the
backing bean.
Now when the inputText is told to refresh (partialTriggers) of course it comes
back with that empty value.
Hm, even though this is not a Trinidad bug, it is very unfortunate for the user.
Do you have any idea for a workaround (i.e. refreshing only the disabled
attribute, but not the value itself)?
> inputText looses its values when switched from disabled to enabled using PPR
> ----------------------------------------------------------------------------
>
> Key: TRINIDAD-1198
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1198
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.9-core
> Reporter: Stephen Friedrich
>
> Title says it all:
> When a disabled text field contains some text, then some PPR action sets
> disabled="false" on that field, then the field losses its value.
> All text is gone.
> See TRINIDAD-1130 for an example app (the bug also still occurs with current
> svn version).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
