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

IE not scrolling via mouse when overflow-y enabled on tt-suggestions #1243

Open
Joseffb opened this issue May 14, 2015 · 5 comments
Open

IE not scrolling via mouse when overflow-y enabled on tt-suggestions #1243

Joseffb opened this issue May 14, 2015 · 5 comments

Comments

@Joseffb
Copy link

Joseffb commented May 14, 2015

Hey all. I'm having a weird problem only in IE (of course) where the tt-suggestions span shows a scroll bar and the minute you click the scroll bar with the mouse it closes menu (I have the click to close in typeahead disabled to allow this).

As far as I can tell the scroll bar is being rendered outside of the tt-suggestions span and when you click the scrollbar to scroll, it thinks your clicking outside the span and hides the entire menu.

Any ideas how to make IE behave in this instance? Asking here because it's a mix between css and typeahead js.

This only happens in IE. In Chrome and Safari you can scroll with mouse just fine. Thanks!

@septagram
Copy link

This happens for me as well, in IE11 :(

Worse yet, if you click on any suggestion in IE8, but slowly (like having ~100ms between mousedown and mouseup), it closes and reopens the menu without registering the click.

septagram added a commit to septagram/typeahead.js that referenced this issue Jul 27, 2015
@septagram
Copy link

Hope this helps.

@Joseffb
Copy link
Author

Joseffb commented Jul 27, 2015

Thanks Septagram. Doesn't seem to work on MS11. I noticed that the comment said <=ie 8 -- maybe this is why ie11 isn't cooperating?

@Joseffb
Copy link
Author

Joseffb commented Jul 27, 2015

Also I'm using typeahead 10.04, not 11. So maybe it's the o.menu entry that isn't working? (not sure).

@septagram
Copy link

I'm not sure if there were structural changes for 10.04 to 11. Do you mean you tried rebasing the fix to 10.04?

And can you please explain how it doesn't work (i.e., typeahead completely broken, does not fix the bug, introduces regressions etc.)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants