]
Alex Kolonitsky updated RF-9641:
--------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Due Date: 21/Jan/11
rich:tooltip - @target is taking clientId, but component.id is
expected
-----------------------------------------------------------------------
Key: RF-9641
URL:
https://issues.jboss.org/browse/RF-9641
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Milestone3
Environment: RichFaces 4.0.0-SNAPSHOT r.19919
Metamer 4.0.0-SNAPSHOT r.unknown
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.29
OpenJDK Runtime Environment 1.6.0_18-b18 @ Linux
Chrome 7.0.517.41 / Firefox 3.6.12 @ Linux x86_64
Reporter: Lukas Fryc
Assignee: Alex Kolonitsky
Priority: Critical
Fix For: 4.0.0.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Currently, tooltip is using clientId for attaching to target component, but in past, the
@for target contained component.id.
The doc isn't clear in this case:
http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/rich_toolTi...
The sample doesn't clarify the difference in usage with regular HTML tags and JSF
components.
<div id="regular-div" class="sample-panel">Div with
clientId="regular-div"</div>
<a4j:outputPanel styleClass="sample-panel" id="jsf-div"
layout="block">
Div with id="jsf-div",
clientId="#{rich:clientId('jsf-div')}"
</a4j:outputPanel>
<rich:panel id="panel" style="width: 200px">
Panel's content 3 (id="panel",
clientId="#{rich:clientId('panel')}")
<rich:tooltip id="tooltip"
target="#{richTooltipBean.attributes['target'].value}">
Tooltip content
</rich:tooltip>
</rich:panel>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: