Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: IndexSizeError: Index or size is negative or greater than the allowed amount #939

Closed
janul opened this issue Feb 18, 2015 · 3 comments

Comments

@janul
Copy link

janul commented Feb 18, 2015

Hi,
first of all - it very nice piece of work.
I have small issue with (at least pie) on tabs (zurb foundation framework)
When chart is set on tab which is not active (hidden) on page load -> then when i click on tab containing chart the chart is not shown - however if even move/resize browser it's ok again

Error: IndexSizeError: Index or size is negative or greater than the allowed amount
Source File: Chart.min.js Line: 10

@seraphx2
Copy link

Chart definitely will not render in a "hidden" area. I am creating an accordion with jQueryUI and when I have a canvas defined inside a closed accordion area, it gives this error. When I put the canvas outside of this, it renders just fine. The one solution I found is to not apply the jQueryUI accordion until after the chart is applied to the canvas and it worked fine.

@antonyf
Copy link

antonyf commented Aug 21, 2015

Hi sorry for the late reply here. I had the same issue with something else.. heres a possible fix for you.

I had the same problem too, drove me nearly nuts. 3 days i spent on this. Check the following: Body height. Not just the css height, but also physically check the height, i use mozilla firebug to select the body attribute, this highlites it. If its above the element, or selection area, it will give the bug Also css for the specific area to select, and body

-moz-user-select: none;
-webkit-user-select: none;
-ms-user-select: none;
Make sure your user selection is !!NOT!! none.

Hope this helps you out.. I did read some veryy frustrating posts regarding this issue, and it was not an easy find either, i found it quite by chance.

@etimberg etimberg added the v1.x label Dec 25, 2015
@etimberg
Copy link
Member

Consolidating with #762 which is related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants