-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[AutoComplete] focus gets lost to Popover in Firefox #2968
Comments
I am having a similar problem in Chrome. For me it occurs when I have more than 1 AutoComplete on screen. The popover is closed immediately because of a onClickAway on the render layer of the popover. It results in very weird behaviour. |
Ok, this is what I observed:
It looks like a timing issue, because when I set a breakpoint after the focus event is received and then lit continu it works fine. |
@alitaheri I don't think this deserves the Cross Browser Support label, it looks like a bug to me. |
Yeah, you're right. Thanks |
I think the issues @hmeerlo and @jeffberry are describing are different. I am also seeing a Firefox-specific UI problem. To reproduce: Step 1. Open Chrome at http://www.material-ui.com/#/components/auto-complete Step 2. Open Firefox on http://www.material-ui.com/#/components/auto-complete Although the page I have referred to has multiple autocomplete widgets, the problem also shows on a page with just the one. |
Thanks for updating this @pdc. Everyone can test the changes in those PRs in our latest alpha since #3356 was included as part of that release. Feel free to reopen this if you are still having this problem. http://www.material-ui.com/v0.15.0-alpha.1/#/components/auto-complete |
So I've been using AutoComplete successfully for the last few weeks in Chrome. Unfortunately our client hates Google and we need to make our app work in Firefox.
It appears that the current AutoComplete loses it's focus in Firefox as soon as the popover opens with results. I tested this on the official Material-UI documentation site as well. I am using the latest version of Firefox (43.0.4) if that helps.
I've been messing with it for hours trying to figure the issue out myself, but can't seem to make any progress.
The text was updated successfully, but these errors were encountered: