{"push_id":825045687,"size":2,"distinct_size":2,"ref":"refs/heads/dev","head":"5f704f0b0fa367440897bb3c711e056eb7b0e0a0","before":"4e208c74ce8844fbe0719a8beeac70d10fca1739","commits":[{"sha":"dea95ec6f6bb0d0acf36eb805aaa8b77d227c1d3","author":{"email":"1accbcc3c5e48d61e4bf2793cf4a5690cbb1ac0a@gmail.com","name":"Lisandro Lorea"},"message":"Better default value for suggestedFps\n\nIn any game that handles fps issues as seen in http://phaser.io/examples/v2/time/slow-down-time the game will hang if game.fpsProblemNotifier fires early on, before game.time.suggestedFps has any value other than null. \r\n\r\nThe docs recommend waiting a few seconds before accesing suggestedFps. Since it's hard to tell exactly how long \"a few seconds\" is, shouldn't suggestedFps be initialized to the same value as desidedFps? \r\n\r\nI think it's better to get an inaccurate value for a few frames than an invalid value. It means users don't have to care about the specifics of how and when suggestedFps gets its value.","distinct":true,"url":"https://api.github.com/repos/photonstorm/phaser/commits/dea95ec6f6bb0d0acf36eb805aaa8b77d227c1d3"},{"sha":"5f704f0b0fa367440897bb3c711e056eb7b0e0a0","author":{"email":"972a13cbbe5e845ecb59dace8e3ece01450d33f4@photonstorm.com","name":"Richard Davey"},"message":"Merge pull request #2130 from noidexe/patch-5\n\nBetter default value for suggestedFps","distinct":true,"url":"https://api.github.com/repos/photonstorm/phaser/commits/5f704f0b0fa367440897bb3c711e056eb7b0e0a0"}]}