-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Type Error in Chrome. Please try the 1st EaselJS demo (flowers). It fails. Please help. #321
Comments
Can you provide more information? I am unable to reproduce this, and would expect it to be widely reported if it was a library issue (since almost every project uses Bitmap). I'm testing with Chrome 27.0.1453.93 OSX. Thanks! |
The issue is that your image hasn't been loaded, wait for the image to be loaded before you create your Bitmap. var img = new Image(); img.onload = function () {
} |
@dynamic-solutions - Sebastian is correct about the issue with your code. You are only updating the stage before the bitmap finishes loading, so it never shows up. I'm at a loss to explain why the daisies demo doesn't work for you though. I'm unable to reproduce, and haven't seen any other reports of it. Could you also provide the full details of the error that is being generated in the console? |
Thanks for the onload code snippet, sebastianderossi Unfortunately the issue remains. Please refer to issue #323. I do believe it is connected. As requested: 1st here are screen shots of flower demo, and console error. 2nd is my code snippet and console error. My snippet causing same error.
// var bitmap = new createjs.Bitmap(this);
And this has just started 5 days ago. |
hmmm... seems strange. Like Grant said before can you give us more information, for instance Have a look at this, see if this runs for you. |
We also saw this error popping up 5 days ago, only in Chrome 27. The code wasn't touched, and it was running flawlessly until then. Our code is still on EaselJS 5.0. |
Hi sebastianderossi, I use jsfiddle also, it stopped working when I 1st reported this. (approx 8 days ago) |
Definitely looks like this is something specific to the latest Chrome on Win7. Not occurring on OSX. We'll look into this, but if you are successful in fixing this or gather more info, please share. |
I've tested in the same version of Chrome (v 27.0.1453.94 m) in Windows 7, and both examples work for me (daisy example + JSFiddle example) with no problem. The variables in the error message you posted are also very unusual. You can see that "p" is defined, and "imageOrUri" is a param. I have to assume there's some kind of parsing error occurring, but without being able to reproduce it, it is nearly impossible for me to narrow it down. Is it possible you have some extension(s) installed that are causing a conflict? |
Removing extensions WORKED!!!
I never used these, and was only interested in what they could be used for. But I have had these extensions for over 12 months. At any case this has worked. Thank you very much gskinner, and all those helping me to resolved this. |
Great to hear! Any chance you could isolate which extension is causing the issue (so we can report it)? Sent from my mobile, please excuse typos & brevity. On 2013-05-27, at 5:49 PM, Aaron notifications@github.com wrote:
|
I've opened an issue with the extension's developer: |
Im aware of this issue as it happened in my project just recently. It seems to be based around the bitmap initialising.
To reproduce: Initialise a bitmap image and add it to stage. It will not display in Chrome. (The Type Error may show in console).
The text was updated successfully, but these errors were encountered: