Results 44 comments of Josh Story

@michaelwarren1106 our plan is to include this in our next stable release which is being put together now. It will be merged closer to when we are ready to publish

superceded by: https://github.com/facebook/react/pull/28069

@domfarolino >I guess I had in mind that the imperative API would force-SPAM-move the "state-preservable" elements in the subtree that's moving I think what Seb is saying is that React...

@sweetliquid the nodeName check is a shortcut to avoid the attribute lookup on link tags since it will likely be slower than just reading the node name. You're right thought...

@acdlite @kassens I was going to approve this test but noticed the assertions had to change with the modern root. Not really sure what this test is for but it...

@kassens @rickhanlonii I rebased on main. This PR removes the flag entirely. Are we blocked on landing this because of RN?

Yeah I suppose edge has implied tighter memory constraints. Do you think the transferred buffers are likely to not be freed quickly? but yes I came to the same conclusion...

>Is a running number really necessary to express this logic? Not for this PR but I expect it to be necessary for the follow up which maybe should land together...

I pushed an update that models this using a schedule state. I think there are still some timing implications once we move to having microtask pings retry synchronously because we...

closing in favor of https://github.com/facebook/react/pull/29491