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

Undefined height/width on canvas element causes browser loop/lock #231

Closed
dohvak opened this issue Sep 30, 2013 · 2 comments
Closed

Undefined height/width on canvas element causes browser loop/lock #231

dohvak opened this issue Sep 30, 2013 · 2 comments

Comments

@dohvak
Copy link

dohvak commented Sep 30, 2013

When adding a canvas element i.e. <canvas id="MyCanvas"></canvas>

Passing in the ID: var ctx = document.getElementById("MyCanvas").getContext("2d");

This results in making the html document non-responsive in Chrome. All interaction within the Tab is ignored. You must close the tab and open a new one for the state change.

Not a high impact bug as it is easily avoided but the result is fairly non-graceful failure and certainly easy to do on accident.

@fulldecent
Copy link
Contributor

I cannot reproduce this on the latest version.

Hello, this issue looks like an ERROR REPORT, for something not correctly implemented in Chart.js. It would be very helpful if you could please create an example chart that would illustrate this missing feature using JSBIN and even attached a mockup here of what the result should look like.

To help, I have created a simple JSBIN which you could fork:
http://jsbin.com/yozobahucero/1/edit?html,js,output

Sorry that this response is templated as we are triaging many issues and ones with test cases will be seen first.

@etimberg
Copy link
Member

etimberg commented Jan 4, 2015

@dohvak I cannot reproduce this issue in the Chrome 39.0.2171.95 using the latest version of Chart.js (1.0-beta4). Since the time that you reported this issue, Chart.js has undergone a significant rewrite. If your issue still persist, please open a new issue and include a link to a JSBin showing your problem. This is the JSBin that I used to test this issue.

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

No branches or pull requests

3 participants