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

Non-actionable warning in console: You tried to return focus to null but it is not in the DOM anymore #11

Closed
coderberry opened this issue Nov 12, 2014 · 6 comments

Comments

@coderberry
Copy link
Contributor

I am seeing a lot of messages in the console: You tried to return focus to null but it is not in the DOM anymore. I am unsure how to make this warning go away.

@misuba
Copy link
Contributor

misuba commented Jan 27, 2015

I'm having this issue still, as well as issues with a text field not keeping its focus in Chrome.

@glifchits
Copy link

@misuba I'm with you there. I get the warning almost every time state most places in my app change, even when the modal is not open.

@jeffutter
Copy link

I am seeing this too. @mzabriskie can we reopen this issue?

@jccode
Copy link

jccode commented Apr 28, 2016

Still seeing this warning too. :(

Reproduce steps:

  1. Construct 2 modals, named it modal_A and modal_B.
  2. Open modal_A (with one button).
  3. In modal_A 's click handler, try to close modal_A and open modal_B.
  4. When you try to close modal_B, you can see the warning messages in console window.

@mrkvngrkn
Copy link

I'm getting this warning since I've upgraded to React v16

@diasbruno
Copy link
Collaborator

@jccode @mrkvngrkn Please follow issue #577. We are discussing how we are going to handle this properly.

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

7 participants