i went with /expand-text, instead of /text-expand, to avoid triggering both /text and /text-expand as you type.
the user still has to click on the page for the Ctrl or Shift key events to fire, which was an intentional choice. that is, for simple implementation, and since the focus stays in the plugin search box. that said, i'm open to looking into automatically collapsing the search box and setting focus on the <body> when /text-expand is typed.
closes #583
my test steps:
npm run dev:extensionconsiderations:
/expand-text, instead of/text-expand, to avoid triggering both/textand/text-expandas you type.<body>when/text-expandis typed.