Effen: willUmount->didUnmount, allow setState after didUnmount

Effen: willUmount->didUnmount, allow setState after didUnmount

This patch changes the timing of the unmount call until after the component is removed (and marked as such) and allows setState to be called after this point. If this happens, setState will still invoke the closer to do any neccesary cleanup, but doesn't schedule the component for render

R=eseidel@chromium.org, eseidel
BUG=

Committed: https://chromium.googlesource.com/external/mojo/+/989d263a2ec47dec540a0ffe7b66df402807f8b5

[rafaelw, 2015-03-06 19:14:38]

rafaelw@chromium.org changed reviewers:
+ eseidel@chromium.org

[eseidel, 2015-03-06 19:26:47]

Seems fine, but why don't you want the _inRenderDirtyComponents safeguard? 
Should it now be  ok to call scheduleComponentForRender during a render()?

[eseidel, 2015-03-06 19:27:09]

lgtm, but I suspect you want to leave my assert.  You're welcome to remove it of
course... :)

[rafaelw, 2015-03-06 19:39:06]

ok. fair enough. i added back the assert (but removed the early return on
assertion failure).

[rafaelw, 2015-03-06 20:24:05]

Committed patchset #2 (id:20001) manually as
989d263a2ec47dec540a0ffe7b66df402807f8b5 (presubmit successful).