Elephant-Vessel

The documentation at http://frisbyjs.com/docs/api/ is using obsolete methods (.create, .expectStatus etc) which cause errors when you are getting started with frisby and pull in the latest stuff (v2). Feels unnecessary....

There is some kind of endless loop that triggers the `ReactDOM.unmountComponentAtNode(getRenderRoot(self, useShadowDom));` in the MutationObserver.  ``` var observer = new MutationObserver(function () { ReactDOM.unmountComponentAtNode(getRenderRoot(self, useShadowDom)); var props = getProps(self);...

I removed the MutationObserver and now everything seems to work as it should. What's the intention there?

> The mutation observer allows the component to update its attributes and slot while Shadow DOM is enabled. So it's not even needed when not using Shadow DOM? If true...

The proposed solution for https://github.com/PixelsCommander/ReactiveElements/pull/101 also seems to solve the problem. Question though, and excuse my superficial understanding of the inner workings of React, is it really a good idea...

Thank you for great work. What's the timeline to get 1.0.0-alpha.0 production ready? M73 is rolling out any day now.

I also noticed that the documentation is not in sync with the current available version, the changes about making shadowDom optional are in the documentation but not published to npm...

I applied the changes from 24ee78abaf6f4dfbebf618b03c058a178f216de4 locally and my application loads incredible slow now, if it will ever finish. The CPU maxes out and the console prints warnings about react-invokeguardedcallback.

Are we getting this or equivalent awesomeness soon?

Are you sure you want to go down an implementational path where "namespaces" can implement interfaces?