-
Notifications
You must be signed in to change notification settings - Fork 21
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
Canvas Black in Chrome #1
Comments
Thanks for reporting this issue! Did you get this on the latest edition of Chrome? Is there any error message in the console? |
Thanks for answering! Google Chrome is the latest version (40.0.2214.111 m) I really appreciate your work! Pano.js is much better than anything else out there. |
Not sure if i closed the issue by mistake.. |
I'm glad you like it :-) A really peculiar problem. I ran tests several times and occationally got this error on Chrome 38 (+ Win7). But it seems do not appear on IE or Firefox. I used to encounter a similar problem on another canvas-heavy application, which not only messed the display but even led to random crashes of Chrome: https://code.google.com/p/chromium/issues/detail?id=277297. I guess both have somthing to do with the instability of Chrome's new kernel since it goes to Blink to take place of the traditional Webkit core. I'll continue to keep attension on this issue. |
That sounds great. Hopefully you can solve the issue. I looked into the raw data again and saw that one picture that works in chrome has a 2:1 aspect ratio at low file size. The one that doesn't work has an odd aspect ratio of around 2.11 : 1 at a higher file size. |
Hi Guys,
I have a problem with pano.js
In Internetexplorer it works fine. with Google Chrome it doesn't with every photo.
The Canvas is showing the chosen color (Chrome) but then goes black an stays like that.
Is there a size limitation with Google Chrome. One picture that works is relatively small (1MB) the other is of higher quality (4 MB)
Hopefully somebody can help me.
Thx,
walter
The text was updated successfully, but these errors were encountered: