The issue here seems to be that Ref effects are called after Update effects below (the latter being the effect to do the mounting). Although, if this is the issue, I'm not sure why it would work in IE11 🤔 ...

https://github.com/facebook/react/blob/13c5e2b53112c1cd77dd52e028a4bb33dc492d1b/packages/react-reconciler/src/ReactFiberScheduler.js#L312-L342

I'm assuming this is to ensure that all refs are guaranteed to be mounted, which seems to make sense. On the off-chance that this isn't a guarantee that React provides then we could just flip the order of effects processing (although this breaks two tests around refs being called at the correct time, suggesting this is a hard constraint). Otherwise, it seems autofocussing would need to be broken away from the mounting process to solve this issue, which seems like an odd thing to do for other reasons.

Edit:
To be clear: the update gets marked here if finalizeInitialChildren returns true (which it does only if the host component needs an autofocus).

https://github.com/facebook/react/blob/8d336aa97e9b514dabe78d8192fd58ccdd99aa7a/packages/react-reconciler/src/ReactFiberCompleteWork.js#L505-L518

That then gets fired on commitMount in the reconciler, which again, makes sense.

Uh oh!

input autoFocus causes focus to be emitted before ref #7769

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions