darkraziel Posted September 29, 2016 Share Posted September 29, 2016 Hi everyone, I just tested the keyboard input examples of Phaser on Microsoft Edge and it doesn't work as it should. Sometimes it won't detect key presses or keep a key pressed down even if I already stopped pressing it. I had the same problem with a game we're developing and I even noticed that some of the old games we've developed have the same problem when testing on Edge. Has anyone else had this problem? Should I raise it as an issue on the repository? Link to comment Share on other sites More sharing options...
bruno_ Posted September 29, 2016 Share Posted September 29, 2016 Its just on edge, other browsers are working fine? Link to comment Share on other sites More sharing options...
darkraziel Posted September 29, 2016 Author Share Posted September 29, 2016 Just Edge. Chrome, Firefox, Safari and Opera work perfectly. Link to comment Share on other sites More sharing options...
Arcanorum Posted October 6, 2016 Share Posted October 6, 2016 I've had some testers of my game mention this problem. The most consistent issue I've noticed is key release events not being fired sometimes, but I can't spot any rhythm to when it happens. Only happens with Edge. Link to comment Share on other sites More sharing options...
Tom Atom Posted October 7, 2016 Share Posted October 7, 2016 I can confirm he same in Edge: - sometimes release event is not sent at all, - sometimes there is big delay before key down event is sent. It is not only in Phaser games, but also in games,where key handling is written from scratch. Link to comment Share on other sites More sharing options...
Brian Jordan Posted October 20, 2016 Share Posted October 20, 2016 Our testers are seeing this too, where keyup events are apparently not getting fired sometimes. Link to comment Share on other sites More sharing options...
eddieone Posted October 21, 2016 Share Posted October 21, 2016 Yes, I just notice this too. It's not a great experience for the player as it makes movement wonky. Link to comment Share on other sites More sharing options...
hayesmaker Posted October 27, 2016 Share Posted October 27, 2016 Don't worry... It's just an Edge case Link to comment Share on other sites More sharing options...
Dr_Syntax Posted December 12, 2016 Share Posted December 12, 2016 I've just noticed this too. Has anyone found a solution / workaround? Link to comment Share on other sites More sharing options...
hayesmaker Posted December 12, 2016 Share Posted December 12, 2016 6 minutes ago, Dr_Syntax said: I've just noticed this too. Has anyone found a solution / workaround? yes. load your thing in Chrome. Link to comment Share on other sites More sharing options...
st0n3vn Posted December 19, 2016 Share Posted December 19, 2016 I've just discovered this issue as well. Still no workaround? Edit: I just found out that the onDown event works correctly on Edge and is a viable alternative. Previously I had a check in update where I listened for pressed input such as: // if (this.cursorKeys.left.isDown && this.inputReleased) { // do something} This was bugged for me on Edge as OP described. However, manually assigning an arrow key and triggering an onDown event works okay for me. For example: this.leftKey = this.game.input.keyboard.addKey(Phaser.Keyboard.LEFT); And then the binding: this.leftKey.onDown.add(() => { // do something }); Link to comment Share on other sites More sharing options...
mattbrand Posted January 24, 2017 Share Posted January 24, 2017 This is still an issue with Edge 14. Thanks @st0n3vn I put your alternative into place! Link to comment Share on other sites More sharing options...
Skeptron Posted February 8, 2017 Share Posted February 8, 2017 Using events does not work for us. Did anybody else cannot get the keyboard to work on Edge? It seems that mostly release events are ignored. Link to comment Share on other sites More sharing options...
Evad Posted March 19, 2017 Share Posted March 19, 2017 After some testing i found out this problem only happens if phaser uses webgl, so if possible set phaser to use canvas on edge and your input should work Link to comment Share on other sites More sharing options...
hayesmaker Posted March 20, 2017 Share Posted March 20, 2017 it was set to canvas Link to comment Share on other sites More sharing options...
Skeptron Posted June 4, 2017 Share Posted June 4, 2017 Yep, error happens with canvas as well Link to comment Share on other sites More sharing options...
Recommended Posts