Chrome is the dominant browsers, for Win 7/8, so its the goto browser for testing for most of us.
True indeed, but given the size of Google and the resources at its disposal you can't help but ask why this ongoing issue has not been solved already, options:
Can't fix it
Don't care - the fix can wait till google is ready
HTML5 is not ready for serious workloads - like games
This isn't a C2 problem but... it is a C2 problem in the end, because we rely on these end tools to export.
Not a C2 problem, but a C2 flaw, because it is 100% reliant on third parties who simply aren't concerned enough to give priority to the bugs they introduce.
HTML5 is designed for the web, fine, we get that, but this situation is critical because the web (Chrome & Firefox being the bulk) currently is broken for HTML5 games.
Sadly this problem is inherent to the web. Browser wars, inconsistencies, and unfixed bugs, have always been the way of the web. It is not likely to ever improve....
So atm, here's the export options:....
The way I see it, the only export option right now is Win8. All the other options are broken.
There's nothing unsolvable here, we should see improve through 2015 and beyond
Now that does sound familiar....
Construct 2 is easily the best 2D game dev tool around (imo) - excellent work flow, frequent updates, prompt bug fixes, new features continually added.
But it constantly gets broken for the most part - if you want the world to play your game - by third party dependencies!!!
This kind of thing is always going to be an issue, has been in the past, is right now, and will again be in the future.
The only option we have, each time the other party creates a bug, is to wait for the other party to fix the problem...
Of course in the meantime you cop the 'what a crappy game' from the would-be player\customer - well that is good for business...