We do not currently check to see if we are navigating to a window that the gamepad will not be able to control. If we add a "filter" function to screen out chrome:// URLs, we can use this to avoid focusing on an uncontrollable window when we:
Switch to the previous tab.
Switch to the next tab.
Switch to the previous window.
Switch to the next window.
Reopen the last closed tab or window.
Moving forwards in history.
Moving backwards in history.
As part of this we might also refuse to close the last window/tab that is controllable. We might also open a controllable window on startup if none is open. Both of these should be configurable.
I didn't end up coming up with an approach to the last closed tab or history, but otherwise this has been merged and will be included in the upcoming 1.0 release.
We do not currently check to see if we are navigating to a window that the gamepad will not be able to control. If we add a "filter" function to screen out
chrome://
URLs, we can use this to avoid focusing on an uncontrollable window when we:As part of this we might also refuse to close the last window/tab that is controllable. We might also open a controllable window on startup if none is open. Both of these should be configurable.