Google have stated they wont be fixing the issue, and mention the monkeypatch fix as a resolution - which I believe Ashley has commented on.
So uh yeah... Backwards compatibility is compromised for standards, it's a bit like chopping your leg off because you'll run faster if you're lighter... Thanks Google.
Develop games in your browser. Powerful, performant & highly capable.
Yes, Google have said they will not fix this. If you are going to go as far as the monkeypatch you may as well just republish the game from a new C2 build (there are lots of other useful compatibility fixes for others browsers like IE11, Firefox, Safari etc).
Hopefully this will not happen again since the new policy is not to vendor-prefix features - they tend to be hidden behind flags instead until they are fully standardised and ready.
Game "space-blaster" has start-up problems with Firefox 31.0. Game goes silent when pressed space and nothing happens.
JoKiv - is that anything to do with this thread? It's not to do with the Chrome 36 changes, right?
Ashley Bug report states that "Does this work in other browsers? Yes". Just thought that it's incorrect statement at a moment. Re-exporting has more priority. Especially when Chrome has "Status: WontFix".
I'm also having problems when playing Airscape on Scirra Arcade on Chrome 36.
Just starred the bug post.