-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support SVG #9
Comments
Well, I implemented by myself. It was way more difficult than I first expected. The major remaining issue is event handlers. |
@dutzi Probably, you want to try it. |
Very interesting approach. There's also a web version of react-native-svg now. |
Hey, thanks for coming here. |
I'm still thinking that it would be easier to map the input props which are coming to react-native-svg to dom in the render(?) thread of RND, than mapping the native properties we're giving to the android and ios native view implementations. That is, replacing the Tag/type in the jsx ( a bit like the serialization example here: https://github.com/react-native-community/react-native-svg#serialize ), or defining new components which don't transform the input props and styles at all, just pass them over from the worker to the renderer. As we aim to conform as close as possible to the svg support in react-dom/web. What are the constraints on communication from the worker to the renderer? I haven't looked into RND in detail yet. I would assume it sends json like setNativeProps, or does it allow full Worker.prototype.postMessage? |
First of all, I might be mistaken. I agree that my current approach is kind of disaster, so definitely desire a simpler solution. |
Since "web" version of svg doesn't work, we need to wait for react-native-svg to support "dom".
software-mansion/react-native-svg#945
The text was updated successfully, but these errors were encountered: