-
Notifications
You must be signed in to change notification settings - Fork 466
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
Do not hide autocomplete on scroll in Firefox #438
Comments
Ok, I did some tests with rc8. The problem not just in Windows but in Firefox.
|
I see, you've got to scroll first before you open the AC and you can see the bug. |
It seems like this happens on Firefox but not chrome, could you confirm Since I can reproduce it I ll be able to show it to a front-end dev and if
|
Yes, it's just Firefox. Chrome, Opera and IE don't have this issue AFAIK. |
Ok, the purpose of having scroll working was for small devices, which are mostly under webkit or ie. Firefox being AFAIK mostly used on desktops, scroll support isn't bloquant. So I'm going to hide the autocomplete on scroll on firefox and release 2.2.0 today. One of my roommates at djangocon said he'll help fixing that but that "this bug sucks so I'm going to really have to take time", so we'll hopefully have that fixed in 2.2.1. Does that sound ok to you ? |
I think this issue can wait till 2.2.1 for sure and I'll be glad if someone will fix that. Please let me know when there are any changes so I can help with testing. |
I've been told by a Mozilla employee that we should report it on their bug tracker anyway because it's firefox-specific. Pretty awesome B) |
The solution we've had works well enough. Please reopen if you have any question. |
Hi, |
Last issue from #431: it has been reported that scrolling with an open autocomplete doesn't work well in windows.
Good news is that I contact BrowserStack support and they said they'd enable our tests on their awesome infra for free ... Because guess what: I don't have Windows so I can't reproduce ^^
The text was updated successfully, but these errors were encountered: