[
https://issues.jboss.org/browse/RF-11783?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11783:
-------------------------------
Description:
The following code resides in the footer of an extendedDataTable, although my
guess is that this is not relevant. The button is initially disabled, then
bean.property is set true and we do ajax render="myButton". The button
disappears from the screen. Removing the tooltip makes it work as expected.
{code}
<a4j:commandButton
id="myButton"
value=" test "
action="apage?faces-redirect=true"
disabled="#{empty bean.property}">
<rich:tooltip mode="client" showDelay="850">
<h:panelGroup layout="block" style="width: 200px; text-align:
justify">
<h:outputText escape="false" value="some text"/>
</h:panelGroup>
</rich:tooltip>
</a4j:commandButton>
{code}
was:
The following code resides in the footer of an extendedDataTable, although my
guess is that this is not relevant. The button is initially disabled, then
bean.property is set true and we do ajax render="myButton". The button
disappears from the screen. Removing the tooltip makes it work as expected.
<a4j:commandButton
id="myButton"
value=" test "
action="apage?faces-redirect=true"
disabled="#{empty bean.property}">
<rich:tooltip mode="client" showDelay="850">
<h:panelGroup layout="block" style="width: 200px; text-align:
justify">
<h:outputText escape="false" value="some text"/>
</h:panelGroup>
</rich:tooltip>
</a4j:commandButton>
Component/s: component-a4j-core
disabled a4j:commandButton with nested tooltip disappears when
enabled with ajax render
---------------------------------------------------------------------------------------
Key: RF-11783
URL:
https://issues.jboss.org/browse/RF-11783
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.1.0.Milestone4
Environment: Mojarra 2.1.3, Glassfish 3.1.1.
Reporter: Brendan Healey
Fix For: 4.3-Tracking
The following code resides in the footer of an extendedDataTable, although my
guess is that this is not relevant. The button is initially disabled, then
bean.property is set true and we do ajax render="myButton". The button
disappears from the screen. Removing the tooltip makes it work as expected.
{code}
<a4j:commandButton
id="myButton"
value=" test "
action="apage?faces-redirect=true"
disabled="#{empty bean.property}">
<rich:tooltip mode="client" showDelay="850">
<h:panelGroup layout="block" style="width: 200px; text-align:
justify">
<h:outputText escape="false" value="some text"/>
</h:panelGroup>
</rich:tooltip>
</a4j:commandButton>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira