phaser: Cannot read property 'shortcutLock' of undefined?
Hi, I created a practice game based on the Phaser tutorial. After I upgraded to the newest Phaser release (Apr 29), I started getting this error when I press keyboard keys in the game:
Error in event handler for (unknown): Cannot read property 'shortcutLock' of undefined Stack trace: TypeError: Cannot read property 'shortcutLock' of undefined at chrome-extension://oknpjjbmpnndlpmnhmekjpocelpnlfdi/js/content.js:32:32 at disconnectListener (extensions::messaging:335:9) at Function.target.(anonymous function) (extensions::SafeBuiltins:19:14) at EventImpl.dispatchToListener (extensions::event_bindings:395:22) at Function.target.(anonymous function) (extensions::SafeBuiltins:19:14) at publicClass.(anonymous function) [as dispatchToListener] (extensions::utils:69:26) at EventImpl.dispatch_ (extensions::event_bindings:378:35) at EventImpl.dispatch (extensions::event_bindings:401:17) at Function.target.(anonymous function) (extensions::SafeBuiltins:19:14) at publicClass.(anonymous function) [as dispatch] (extensions::utils:69:26) extensions::event_bindings:383 EventImpl.dispatch_ extensions::event_bindings:383 EventImpl.dispatch extensions::event_bindings:401 publicClass.(anonymous function) extensions::utils:69 dispatchOnDisconnect
Is this PEBCAK or is there an issue with the input recognition?
My code is here: https://github.com/cattsmall/Phaser-game/blob/master/scripts/game.js
You can try the game and see the console here: http://cattsmall.github.io/Phaser-game/
Thanks for making such a great framework! I’m really excited to share it with my class.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 19 (1 by maintainers)
@alanguir Thanks for the update, I think this has to do with the way we do the “key chording” (allowing for an almost arbitrary number of concurrent keys for a given shortcut) and the listeners involved. I’m going to take a look at this as soon as I can, just a bit swamped right now.
for those asking about which extension: like @cattsmall, I had an exception pointing to
chrome-extension://oknpjjbmpnndlpmnhmekjpocelpnlfdi/js/content.jsoknpjjbmpnndlpmnhmekjpocelpnlfdiseems to be the Chrome-store ID for the Readability extension, which I have installedhttps://chrome.google.com/webstore/detail/readability/oknpjjbmpnndlpmnhmekjpocelpnlfdi?hl=en
Hey everyone, I’ll take a look at why this is happening and fix the extension on our end as well. Sorry about that!
Philip (from Readability)
@philipforget I’m still seeing this error. Is there a fix planned?
@philipforget is the guy from readability. He’s helping to fix it. 👍
All bugs lead back to me
I can confirm I’m getting this same error in chrome coming from readability while trying to read keypress events in Angular 1.5.
Interestingly, if you view the readability options page then the plugin stops listening for keypresses. This is somewhat less annoying than turning the plugin off and on again while developing.