Sebastian Markbåge 4804518c26 Handle nested controlled events (#8251) ...

I came up with a contrived case of where nested controlled events could
fire within the same batch - but on different targets.

I think we came to the conclusion that controlled values typically cannot
use preventDefault so it is ok that they don't flush until after the event
has finished. So therefore we accumulate a queue of all the nested targets
within a batch and then restore state on all of them.

I'm still skeptical that this is the correct way to do controlled values.
The reason we have to do them in a single event loop is because when you
type, the sequence of values that get accepted or not can matter. I wonder
if there is a scenario we can come up with where you can fire multiple
inner events in an event loop and end up with batching causing problems.

This effectively just reimplements asap again but with no allocations for
a single target and no closure allocations.

2016-11-11 16:49:59 +00:00

..

babel

Make React.__spread warn

2016-04-07 17:30:23 -07:00

bench

Fix benchmarks (#7704)

2016-09-12 21:58:00 +03:00

error-codes

Fix error codes (#7999)

2016-11-08 20:20:46 +00:00

facts-tracker

Introduce facts-tracker (#7747)

2016-09-26 12:58:51 -07:00

fiber

Handle nested controlled events (#8251)

2016-11-11 16:49:59 +00:00

git

Remove leftover env variable logic in pre-commit hook

2015-09-01 14:35:47 -07:00

jest

Track passing/failing tests in fiber (#8169)

2016-10-31 23:26:38 -07:00

perf-counters

Year-agnostic copyright message, like React Native uses, to prevent the need for yearly changes.

2015-12-29 20:20:32 +01:00

authors

AUTHORS

2013-09-09 23:42:54 -07:00