facebook/react — pull request #1987 by syranide (2014-08-03 10:28:47+00:00)
Title: Provide a friendly path for reactID errors in ReactMount

Dissected from my #1570

Provides a human friendly path instead of just a rather opaque reactID. Chrome still has intermittent issues with long error messages being truncated, but this is supposedly fixed (again) in Chrome 37. No other browsers should have issues displaying the full error message.

Now that we have friendlier error messages, how far do we want go to "resolve" implicitly added DOM? Personally I feel like we should get rid of the "blind jumps" we do now (primarily missing `thead`), it seems like unsafe behavior and it would be preferable for users to just be notified of the issue instead (technically, they provided *invalid* markup).

```
Invariant Violation: findComponentRoot(..., .0.1.0:0:0.0.0.0.0): Unable to find element. This
probably means the DOM was unexpectedly mutated (e.g., by the browser), usually due to forgetting
a
when using tables, nesting tags like

,

, or , or using non-SVG elements in
an