Scirra should have just answered the post with a simple statement that they have no time\desire to do what the OP was requesting.
Despite the rhetoric here, both C2 and C3 rely on third party components either to run in a browser or to run on any other medium.
C2 and C3 are great for browser games - like well they are HTML5, but for any other type of use they are only good for prototyping.
If you are serious about making games that do not run in a browser you have to use other tools - it is that simple.
While the event system is awesome, sometimes you just have to bite the bullet and learn other tools, which will require coding.
Despite the fact that Chrome is an awesome piece of engineering (apparently), Google like any other company out there simply DON'T care about how others use their tools\products - the jank problem was absolute proof of that. Firefox, or any other browser maker will be no different.
As already said, there is a reason why the big devs have moved on to other tools to develop their games, which amazingly are still the pull-strings on the home page - think about it....