OK, should be fixed in r79.4 now?

fixed. big thanks!

I was trying to update my signature, when helloworld global number was divided by zero and this happened :(

<img src="http://static2.scirra.net/images/500.png" border="0" />

The number of plays in my badge and in the category list displays "2 plays" since the day before yester day. the rating displays 7 votes though, so I believe there were more plays actually :) Of course under the game canvas on the game page (and in the stats) it displays "324" wchich I believe is correct number of plays.

Got it, thanks. Also I uploaded a new gravatar 3 days ago and it doesn't show yet.

In the forums when you paste html into your signature, it displays as text with html tags as I believe shouldn't be because in the arcade you can create a hame signatures for the forums. Also every time I update my game I have to remove html <br/> tags in description.

"pocket god":

99 cents

18000 downloads during the best one day

circa 300000 android downloads

circa 300000 appstore downloads

dunno how much revenue from facebook version

since august 2011

gives about $600000 in one year

does that answer the topic's question? ;)

idea is everything. not beautiful graphics, nor gameplay experience (well, maybe a little) but the idea!

actually I can and hereby I do confirm, that this fix also works on Facebook iframe apps :)

Terrible, but it's mainly true. nevertheless i think that html5's growth speed and spread compared to flash some kind of stagnation will make it a primary game engine through canvas and javascript in no time, I also give html5 1 - 2 years before it's more adopted than flash.

Here's a quick fix, a new runtime.js for the Mouse plugin:

http://dl.dropbox.com/u/15217362/mouse-iframefix.zip

This won't affect the Arcade since it uses the original r79.3 runtime, but can you give it a quick spin on a Facebook or Kongregate game and see if it helps? Note the app cache might mean you have to refresh twice (check the browser console for app cache activity).

that fix helped for kongregate, so I believe it will also make facebook games work, thanks Ashley you can't imagine my happiness right now :) one thing though, now why use broken runtime on arcade? i understand that it fixes the sticky keys, but i personally believe it's a less of a problem than keyboard not working :)

alemar the problem is still the same, when the game is launched in iframe (facebook, scirra arcade, kongregate) the keyboard plugin doesn't work when used with mouse plugin. when NOT in iframe (preview, exported html5 web site) these two work just fine. still waiting for the fix as the latest r79.3 didn't fix it, despite what's written in the release info:

Games in an iframe (Scirra Arcade, Kongregate...) couldn't get keyboard input due to the workaround to the Chrome 'sticky keys' bug - the only solution is to disable the workaround in this case, so iframed games might still get sticky keys - it may be properly fixed by Google in Chrome 18 anyway.

at least I don't know what "the only solution is to disable the workaround in this case" means, if i knew, I would disable it and it would work, right? :) so maybe the real question here is how to disable the workaround (and what IS workaround) to the chrome 'sticky keys'?

Ashley ok, I can confirm that minifyer and families bugs are fixed, but still the game won't work with keyboard object and mouse object together. is there any way to make it work again like in r78? maybe an option to enable/disable the sticky keys workaraound, some games must have mouse and keyboard and don't use shift or other windows sticky keys.

1) I think I've traced this to the workaround for the Chrome 'sticky keys' bug. The workaround prevents iframes from getting focus which means they never get keyboard input. So I've disabled the workaround when in an iframe, which unfortunately means iframed games will still get the sticky keys bug in Chrome... but I think they've finally fixed it in the next release (Chrome 18) anyway.

Ashley fyi, this problem also exists on Firefox 10.0.1 in my case. is there nothing that can be done on the construct side, we're bound to waiting for a browser update? thanks for clarifying the rest and on quick .2 fix (shouldn't it be 79.1? as 79 is 79.0 I believe :)

edit: ah, the 79.3, installing and checking it out...