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

Firefox on Android compatibility #411

Closed
krikunts opened this issue May 5, 2015 · 7 comments
Closed

Firefox on Android compatibility #411

krikunts opened this issue May 5, 2015 · 7 comments
Milestone

Comments

@krikunts
Copy link
Member

krikunts commented May 5, 2015

Autocomplete doesn't work on Firefox on Android (tested on v. 37.0.2). It sends input event instead of keyup so typing doesn't trigger completion. It would be nice if input event will trigger completion the same way as keyup.

@jpic jpic modified the milestone: 2.2.0 May 15, 2015
@jpic
Copy link
Member

jpic commented May 17, 2015

Closing because there's a PR, please follow #418

@jpic jpic closed this as completed May 17, 2015
jpic added a commit that referenced this issue May 23, 2015
@jpic
Copy link
Member

jpic commented May 26, 2015

Could you try with 2.2.0rc1 which was released yesterday ?

Thanks.

@krikunts
Copy link
Member Author

This particular issue is fixed in 2.2.0rc1. Thank you for the fix.
But I see more strange issues with this update:
First of all completion is broken because of undefined variables isOpera and isIE in autocomplete.js
Lines 82 and 86
Lines 63 and 67
The second thing is when I use autocomplete input with bootstrap modal dialog, choices are displayed behind it.

@blueyed
Copy link
Member

blueyed commented May 26, 2015

For reference, the isIE stuff has been added in 61e54ee.

@blueyed
Copy link
Member

blueyed commented May 26, 2015

@lucky-user
Can you please create new, separate issues for what you've discovered?
Thanks.

@jpic
Copy link
Member

jpic commented May 26, 2015

This needs to be backported from django admin I'm in the car going to
openzfs meet-up right now so I can't right now
Le 26 mai 2015 18:27, "Daniel Hahler" notifications@github.com a écrit :

@lucky-user https://github.com/lucky-user
Can you please create new, separate issues for what you've discovered?
Thanks.


Reply to this email directly or view it on GitHub
#411 (comment)
.

@krikunts
Copy link
Member Author

I created new issues, please follow #425, #426

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

No branches or pull requests

3 participants