Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent Ctrl-Tab from triggering tab completion #541

Merged
merged 1 commit into from Aug 6, 2016
Merged

Prevent Ctrl-Tab from triggering tab completion #541

merged 1 commit into from Aug 6, 2016

Conversation

hho
Copy link
Contributor

@hho hho commented Aug 4, 2016

Fixes #529

This is probably the simplest workaround for Firefox sending a keydown event when switching browser tabs via Ctrl-Tab

Fixes #529

This is probably the simplest workaround for Firefox sending a keydown event when switching browser tabs via Ctrl-Tab
@maxpoulin64 maxpoulin64 added Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. second review needed labels Aug 4, 2016
@maxpoulin64
Copy link
Member

Yeah, this is a pretty cheap fix, but we don't have a key bind on that so that's 👍 for now until we can get a better library I guess.

I see that preventDefault was used, I wonder why that doesn't work with the new textarea...

@astorije
Copy link
Member

astorije commented Aug 4, 2016

Before +1ing this, I would like to understand why this was working just fine on an input element but not a textarea. It may be browser weirdness because it's fine on Chrome (what about IE/Edge and Safari?), but it may also be our code that doesn't work well with textareas...

@hho, did you investigate a little bit there by any chance?

@astorije astorije added this to the 2.0.0 milestone Aug 4, 2016
@hho
Copy link
Contributor Author

hho commented Aug 4, 2016

@astorije 2.0.0-pre.4 doesn't even have a <textarea> yet, does it? It seems to be only a Firefox bug, and an old one at that. I actually don't know how this ever worked in FF… ¯\_(ツ)_/¯

@astorije
Copy link
Member

astorije commented Aug 5, 2016

Indeed, and that's why I was willing to investigate why it works fine with an input but not with a textarea.
But if you found that it's a bug specifically on textareas...

@hho
Copy link
Contributor Author

hho commented Aug 5, 2016

I'm sorry, but I don't understand:
2.0.0-pre.4 uses <input> and it doesn't work correctly with Firefox (this PR fixes that).
To me, this doesn't seem to have anything to do with textareas at all?

@astorije
Copy link
Member

astorije commented Aug 6, 2016

Woosh, my bad! When I tested, I could trigger this bug on <textarea> elements but not <input> elements, which is why I had marked this as a regression, but I guess it's not.
Thanks for sticking with my slowness 😅

@astorije
Copy link
Member

astorije commented Aug 6, 2016

👍 and merging, but let's open this to https://github.com/erming/tabcomplete to avoid monkey-patching libraries Done.

@astorije astorije merged commit 9d5f6f0 into thelounge:master Aug 6, 2016
@astorije astorije removed the priority label Aug 6, 2016
astorije added a commit to astorije/tabcomplete that referenced this pull request Aug 6, 2016
matburnham pushed a commit to matburnham/lounge that referenced this pull request Sep 6, 2017
Prevent Ctrl-Tab from triggering tab completion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants