]
Jay Balunas updated RF-11162:
-----------------------------
Fix Version/s: 3.Future
dynamically-enabled commandButton doesn't work (need
a:htmlCommandButton?)
--------------------------------------------------------------------------
Key: RF-11162
URL:
https://issues.jboss.org/browse/RF-11162
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.3.1
Environment: Seam 2.2.0.GA, Richfaces 3.3.1, and JBoss 5.1.0
Reporter: Tom Bryan
Fix For: 3.Future
Attachments: TestCommandButton.xhtml, TestCommandButtonAction.java
When an h:commandButton is initially rendered as disabled and then dynamically-enabled
during an a:commandButton, it does not seem to submit the page. Changing the
h:commandButton to a h:commandLink gives the same results, but changing it to an
a:htmlCommandLink does work. I'm not sure whether h:commandButton is supposed to work
in this case or whether there should just be an a:htmlCommandButton.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: