The shortcut wasn't defaulted correctly, and additionally, there was no default being set by content.js which slowed down functional loading and hid wave state. The shortcut toggle may still accept any input if left empty intentionally - idk if we want to change that yet.
Added permissions as activeTab wasnt available on contentjs - fixed shortcut default.
The shortcut wasn't defaulted correctly, and additionally, there was no default being set by content.js which slowed down functional loading and hid wave state. The shortcut toggle may still accept any input if left empty intentionally - idk if we want to change that yet.
Added permissions as activeTab wasnt available on contentjs - fixed shortcut default.