Thank you for your feedback. No way to know "tab usage history" for the add-on until it's installed, as there's no built-in API for that and so tab selections must be tracked with custom code. Nice hint about the overridden text-editing functionality, I completely overlooked it: maybe a solution would be checking whether a content-editable element is currently focused and ignoring the keystroke in that case.