Closed duhrer closed 7 months ago
I'm tempted to leave this one until after the config panel is refactored, as I'd like to think about how to make vibration configurable. We can still do it per action, but even that will probably be easier when we restructure a bit (adding one more setting that only some actions use just adds complexity at the moment).
This actually needs to be addressed as a more general problem with a more general solution. Closing this out in favour of #116.
If you open a new window/tab with a keyboard, it may very well be the chrome start page. We cannot inject our scripts into this page, so if you navigate back far enough in history, you lose the ability to control the window until you get a mouse/keyboard.
It would be better to inspect the history and give vibrational and onscreen feedback instead of navigating back to a
chrome://
page.