Add hack to allow users to still add annot comments, tags

[poltak]

• addresses Can't type text in annotation card, or select tags that contain Twitter page shortcuts #722
• overrides default keydown event handling in a hacky way, but it seems to make things work again from user POV which I feel is the main thing for now
• does this break anything? (@oliversauter if you have time, it would be good to get your feedback testing this)
• @ShishKabab @digi0ps @MOHITSAKHUJA it would be great to get your thoughts on this issue, this quick hack, and ways to address it in the long-term (I had one idea in this comment, but not sure if I'm on the right track: Can't type text in annotation card, or select tags that contain Twitter page shortcuts #722 (comment))

[blackforestboi]

thanks for getting this on so quickly. It works only partially so far.
When using it on Github with 's' (which would start searching) I can type the first character, but the focus is then set to the search bar and the next letter is then searched for.

Thats already an improvement, as before it would immediately jump to the search bar.
Maybe we can block every character from being propagated up, or set the focus back to the text field after each character?

[poltak]

Just updated that and it seems to behave on GH now.
Google maps still somehow doesn't work. There's probably less people annotating text there, though it means that there's probably other sites that it doesn't fix it on.

[blackforestboi]

ok, will give it another test. Here is something I stumbled over where they talk about this issue on google maps: https://stackoverflow.com/questions/48893262/google-maps-does-not-relinquish-key-presses-to-input-in-shadow-dom

[poltak]

I saw that too, but it seems to be with the maps API rather than the actual website.

[blackforestboi]

ah ok. Found another couple of interactions with the GitHub keyboard shortcuts.

? calls the help screen
and cmd+c/a/v/x cannot be used. Just ignores it.

[poltak]

and cmd+c/a/v/x cannot be used. Just ignores it.

That should be fixed.

? calls the help screen

For whatever reason I can't get it to work for the question mark :S

I also added a commit to remove the sentry setup from the content script. It was capturing errors that happened on any random website and sending them to our sentry server. Maybe there's a way to detect our own errors we can implement later.

[blackforestboi]

Merging this to be ready for release.