[
https://issues.apache.org/jira/browse/TRINIDAD-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626724#action_12626724
]
Stephen Friedrich commented on TRINIDAD-1198:
---------------------------------------------
Yes, like I said this isn't a Trinidad bug - sorry for reporting this as an
issue.
I wonder how I can update the required attribute without updating the value?!
IMHO this is another point were JSF makes simple things too hard (with JSP I
could simply use javascript without involving the server).
I think I'll try to still do the autosubmit using PPR (so that the component
tree on the server side is updated correcty), remove the partialTriggers
attribute from the inputText and use javascript to manually change the disabled
state (though I am a little afraid of interfering with Trinidad javascript code
that handles the attribute).
> 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.
