Community
Participate
Working Groups
See the attachment, tooltip is shown the script in the Tooltip Text setting when mouse over the marker on the legend. This issue happens in line chart, not in bar chart.
Could you please attached the screenshot and the report design?
Created attachment 174646 [details] Report Design Added report design.
Created attachment 174647 [details] Screen Shot Added screen shot.
According to the screenshot you attached, the tooltip is defined on the legend? The tooltip on legend only support plain text, so the behavior is correct. And tooltip defined on Value series works correct using the scripts you attached in the example. I tired on the 2.6.0 release and latest 2.6.1 nightly build.
No, the tooltip is not defined on the legend, please see my attached report design. I use 2.5.2.
(In reply to comment #5) > No, the tooltip is not defined on the legend, please see my attached report > design. I use 2.5.2. I tried the report you attached with 2.5.2 release build <2.5.2.v20100210-0630>. And the tooltip just worked fine. Please see my attachment. And it's wired that in the screenshot you attached, the tooltip appeared around the legend area. If the mouse is over the markers which has defined script, the tooltip should appear around the line markers.
Created attachment 175207 [details] screenshot with 2.5.2 release
Yes, when the mouse moves over the data point on the line, the tooltip shows up correctly. However, if the mouse is over the markers on the legend, it shows the script (see my screen shot), which shouldn't show anything at all. This weird behavior only happens in line chart. I haven't tried 2.6, but it's there in 2.5.2.
(In reply to comment #8) > Yes, when the mouse moves over the data point on the line, the tooltip shows up > correctly. However, if the mouse is over the markers on the legend, it shows > the script (see my screen shot), which shouldn't show anything at all. This > weird behavior only happens in line chart. > I haven't tried 2.6, but it's there in 2.5.2. I do can reproduce this issue in 2.5.2 and 2.6.0 release now. But I tried with the latest 2.6.1 build (20100727-0630), it seems this issue has been fixed. Would you please download the latest 2.6.1 build and have a re-try?