Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ref-callback life-cycle order issue
See original GitHub issueI’m trying to auto-focus and auto-select an <input type="text"> via the ref property, and was surprised to find that ref gets invoked prior to value getting populated on the same element.
Working example in React:
https://codesandbox.io/s/38k089rxkm
Same example in Preact:
https://codesandbox.io/s/v6406xj99l
Under Preact, calling el.select() has no effect, because the element has no value yet.
Now, I could just defer with setTimeout() or whatever, but this appears to be a potentially substantial inconsistency from React, so I thought I should report it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mindplay-dk Oh no that was done by accident. I just merged the new
refimplementation in our private repo for the next major release and because I mentioned this issue it got closed here… Wasn’t aware that GitHub allowed closing issues from other repos.@mindplay-dk all good points. I think we should be able to switch back to invoking refs as part of the element lifecycle rather than during property diffing.