-
Notifications
You must be signed in to change notification settings - Fork 6
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
Does not work on ipad/safari #3
Comments
Cool game, thanks for doing it! |
Hey @winkler1 ! Thanks! I can't test this now as i don't have a iOS device right now but i'll surely do later! |
mmm... well, the Start button hilights but the game does not start. In chrome with device emulation, the game starts fine for both iPad and iPhone emulation. I'm thinking there must a JS error happening, unsupported API or something. Maybe es5-shim. I'll try to add that in and test with it later. |
Connected to the ipad from Safari to see what's happening on the device... yup, it's http://moduscreate.com/enable-remote-web-inspector-in-ios-6/ Error in main.js#6432. ReferenceError: Can't find variable: Promise |
Oh, thank you so much! @winkler1 . That's comming from the Dispatcher implementation (
I'm not polyfilling it nor using a lib, which is causing this issue. I don't have any apple product here, i'd appreciate a bunch if you could test if adding a polyfill (maybe https://github.com/jakearchibald/es6-promise) would make it 😺 . Didn't know either that that was possible with safari, great :))) |
Throwing this into index.html lets the game start- <script src=" https://raw.githubusercontent.com/paulmillr/es6-shim/master/es6-shim.js "></script>Different error now :) Are you on a Mac? Perhaps the ipad simulator would help - On Thu, Oct 23, 2014 at 9:09 PM, Ciro S. Costa notifications@github.com
http://twitter.com/#!/winkler1 |
Cool! another thing that's matter of polyfilling. The bad thing is that it will fallback to (setTimeout) loop. I'm currently on a low-end Linux 😢 hahaha |
Needs React.initializeTouchEvents(true) ?
The text was updated successfully, but these errors were encountered: