New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Remove setNativeProps API" change #2633
Comments
setNativeProps never worked correctly on web and had undefined behaviour on native. If the fabric implementation has defined behaviour, there's still no reliable way to implement it on web while styles are not simply inline styles. The primary use case of setNativeProps was updating styles without a render, but it's just not reliable on web. Things like text input animations aren't done this way on web either. The new RN architecture will eventually allow for sync events and sync updates, providing the same event loop model as web, so the setNativeProps pattern will likely have fewer reasons to be used on native |
@necolas I appreciate the technical concerns here—thank you!—and I'm sure it's not easy to convey without the reader already having some context around the implementation. From my point of view, I have previously tried to remove Do you think there's some way forward where a "use at own risk" type API is introduced for |
|
@jonathanj For now I think you could use |
Is there an existing request?
Describe the feature request
Back in March last year, the setNativeProps API was removed, since back then the react-native team said that the API would not be supported in Fabric.
This changed as of now as it can be read here.
It would only make sense to get setNativeProps API back into react-native-web again since many people are relying on the API (for example for text input animations) and it is now officially supported in Fabric after react 0.72.
There is also a discussion about this here, where many people agree that this would be the best change.
The text was updated successfully, but these errors were encountered: