For actions such as recording and sending, we should allow mouse click on the keyboard shortcut itself. So it's this modality where everything is keyboard-first, but some humans and industries will need to click on things because they don't know how to use their keyboards yet. And if we don't provide this, they may instantly give up.
We may need to re-architect our structure since we currently have display components that are not in charge of triggering actions, and it's quite spaghetti.
For actions such as recording and sending, we should allow mouse click on the keyboard shortcut itself. So it's this modality where everything is keyboard-first, but some humans and industries will need to click on things because they don't know how to use their keyboards yet. And if we don't provide this, they may instantly give up.
We may need to re-architect our structure since we currently have display components that are not in charge of triggering actions, and it's quite spaghetti.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For actions such as recording and sending, we should allow mouse click on the keyboard shortcut itself. So it's this modality where everything is keyboard-first, but some humans and industries will need to click on things because they don't know how to use their keyboards yet. And if we don't provide this, they may instantly give up.
We may need to re-architect our structure since we currently have display components that are not in charge of triggering actions, and it's quite spaghetti.
Reopening as many still do not work:
Think about architectural changes required here.