Turns out a lot of people are having the same issue with Chrome / Chromium and their extensive security. Not that I mind a lot of great security around JavaScript, mind you.
http://code.google.com/p/chromium/issues/detail?id=40787
Hopefully once the game makes it out to the web this will go away as it’s the same domain policy that’s causing problems.
Turns out Chrome DOES have a Javascript error output console: CTRL+Shift+J.
Thank heavens.
BastardBlaster is not running in Chrome because of this:
Cross origin requests are only supported for HTTP.
At least now I have some direction on where to head.
Thanks Guelph Game Jam!
I couldn’t figure out why my HTML5/JS Akihabara game was not loading and thought the error in the Firefox JavaScript Error Console “Not well formed” had something to do with it. Turns out that if Akihabara cannot find the audio files for your game, it hangs on loading and there is no error in the console to that effect.
I threw the OGGs and MP3s in the directory and we’re off to the races. Still get “Not well formed” but the game runs. Who knows?
20 minutes blown trying to figure out why I couldn’t include JS files from ../ in the <head> tag. *sigh* Chrome needs the Javascript error output window that Firefox has.
Almost have the game loading, however. Making progress.
Note for anyone who is working on an Akihabara JS game: making a directory inside the unzipped Akihabara directory then trying to include the Akihabara files by ../akihabara/*.js does not work as JS in the browser cannot access stuff outside of its own domain.
