It's interesting that shortcut keys *must* be two or more keys in combination, but certain characters can't be used e.g. Ctrl+2 will go to your second tab if you have one, which is in direct contradiction to the "will override browser behaviour" statement in the documentation; Ctrl+# won't work at all... If you have multiple actions that use the same shortcut, the first that is registered will be triggered. I'm assuming that across multiple modules it'll be the one in the earliest module sorted alphabetically by app ID (as event subscriber procedures do).
It's interesting that shortcut keys *must* be two or more keys in combination, but certain characters can't be used e.g. Ctrl+2 will go to your second tab if you have one, which is in direct contradiction to the "will override browser behaviour" statement in the documentation; Ctrl+# won't work at all...
If you have multiple actions that use the same shortcut, the first that is registered will be triggered. I'm assuming that across multiple modules it'll be the one in the earliest module sorted alphabetically by app ID (as event subscriber procedures do).
In your test at 9:05 you typoed Alt-Q instead of Alt+Q. I tested it with Alt+Q and it did not work.
Good eyes... I did try it earlier and that did work either....
In earlier videos, after start with debugger, you needed to login with id+password. In this video you are autologged in. How?
You mean in VS code or in the browser?
@@Hougaard in the browser
That's just a matter of the browser cookies status...
@@Hougaard ok, so maybe my lastpass is preventing this cookie