Visualization tooltip border gets cutoff for chart endpoints. about google-visualization-issues HOT 9 CLOSED

this issue fixed?

I'm seeing this issue, but it's not just the border that's getting cut off. By creating
an AreaChart with width 600 and the chartArea width set to 600 (creating a chart maximized
to its container), about half the tooltip gets cut off for data points at the far left
and right sides. I think it's a matter of the tooltips going outside the chart's container
(and iframe, for that matter), and for some reason the javascript doesn't know to move
the tooltips over.

I'm using gwt as well.

I am getting the same issue as "armil". This issue starting occurring today. It used
to be that the tooltip was drawn inside the chart area, therefore not getting cut off.
But that doesn't seem to be the case anymore, it just draws them without any limits.

I'm using version 1 and using the controls package. And this problem occurs in Firefox
6.0 and IE 8

You can see the effect of the cut-off tooltip from this example: http://code.google.com/apis/chart/interactive/docs/gallery/controls.html#overview

If you mouse over the "Margareth" pie slice, it gets cutoff from the left. It used
to just be totally drawn inside the chart area not being cut off.

Given this bug has been open for two years, is there any chance of the google visualizations
codebase being open sourced so that users like us could poke around and try to fix
this?

I understand it's an internal google project, and so you might do something similar
to GWT where the "master" source repo stays in google's infrastructure and is only
accessible to google engineers.

But given this is just a client-side javascript library, is there any harm in open
sourcing a non-obfuscated version so we could potentially submit patches?

Please don't confuse the original issue from two years ago, which is probably referring
to the old linechart (which was replaces by 'corechart' linechart), to the new issue
that was just introduced yesterday. After we'll fix the new issue, we can have a look
at the old issue, and my guess is it's not an issue any more.

IOW, it's quite possible this bug was fixed long ago, but not marked as such (our bad).

Ah, my apologies. I didn't realize this was a new bug. I assumed it'd been happening
for quite awhile, and I just hadn't noticed it before. Thanks!

Do we need to open a new bug on this for the new problem?

This should have fixed by now. Sorry for delay.

Looks great, thanks!