Uploaded image for project: 'RichFaces'
  1. RichFaces
  2. RF-9641

rich:tooltip - @target is taking clientId, but component.id is expected

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 4.0.0.Milestone3
    • Fix Version/s: 4.0.0.Milestone6
    • Component/s: None
    • Labels:
      None
    • Affects:
      Documentation (Ref Guide, User Guide, etc.)

      Description

      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_toolTip.html
      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>

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Alex.Kolonitsky Alex Kolonitsky
                  Reporter:
                  lfryc Lukáš Fryč
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Due:
                    Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 2 hours
                    2h
                    Remaining:
                    Remaining Estimate - 2 hours
                    2h
                    Logged:
                    Time Spent - Not Specified
                    Not Specified