You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nowadays browser is the main interface for almost everything. It's not about 'browsing' anymore, but rather building workflows using extensions and global shortcuts. Keyboard is the dominant way of interacting, and not only for power users.
Recent versions (after 1.70.119 Chromium: 129.0.6668.70 (Official Build) (64-bit)) completely brake the system of removing/reassign Default Brave Keyboard Shortcuts which in turn broke all workflows.
It would be great to move it back.
There is identical issue, but it was closed without comments/addressing the issue in any way. People were asking about reasons of closing, but alas no answer.
Steps to reproduce
Try to delete any default shortcut using 1.70.119 Chromium: 129.0.6668.70 (Official Build) (64-bit)
Try to do the same with any later version
Feel how painful is to use Brave now, while it brake everything
Description
Nowadays browser is the main interface for almost everything. It's not about 'browsing' anymore, but rather building workflows using extensions and global shortcuts. Keyboard is the dominant way of interacting, and not only for power users.
Recent versions (after 1.70.119 Chromium: 129.0.6668.70 (Official Build) (64-bit)) completely brake the system of removing/reassign Default Brave Keyboard Shortcuts which in turn broke all workflows.
It would be great to move it back.
There is identical issue, but it was closed without comments/addressing the issue in any way. People were asking about reasons of closing, but alas no answer.
Steps to reproduce
Actual result
no need
Expected result
remove/change shortcuts
Reproduces how often
Easily reproduced
Brave version (brave://version info)
Brave is up to date
Version 1.73.105 Chromium: 131.0.6778.265 (Official Build) (arm64)
Channel information
Reproducibility
Miscellaneous information
No response
The text was updated successfully, but these errors were encountered: