"TypeError: Cannot read property 'getAttribute' of null" form component without dom node about rquery HOT 6 CLOSED

I've never seen findDOMNode return null unless there's an error in your rendering. The render function must ALWAYS return an element, so every component must had a DOM node.

My suspicion is that your DOM tree is being modified by the browser, which would normally cause an invariant violation as well. See here: http://stackoverflow.com/questions/25026399/uncaught-error-invariant-violation-findcomponentroot-110-unable-to

In any case, I need an easily reproducible example in order to be able to fix anything. findDOMNode always returns a value for valid React trees.

from rquery.

Not a bug in rquery, from what I can tell.

from rquery.

Why the render function must ALWAYS return an element?
The documentation says that the render function may return null

You can also return null or false to indicate that you don't want anything rendered. Behind the scenes, React renders a <noscript> tag to work with our current diffing algorithm. When returning null or false, ReactDOM.findDOMNode(this) will return null.

from rquery.

Hmm, I had missed that change in the React spec. In previous versions render was definitely required to return something.

from rquery.

Fix released as version 4.3.0. Hopefully that works for you. Thanks for the bug report!

from rquery.

Yes, its works for me. Thank you!

from rquery.