Ok, I’ll say it: if web components need React’s support to be successful, maybe that says more about WC’s design than any supposed nefarious intent from the React team.
-
Show this thread
-
-
Replying to @justinfagnani @AdamRackis
Web components didn't invent addEventListener or properties. They're low level basics that existed before React. React doesn't support them and it's really all on React and not web components.
1 reply 0 retweets 5 likes -
Replying to @justinfagnani
React will expose raw dom nodes anytime you ask it to, so I think I’m missing your point. Can you elaborate?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis
How do you set an arbitrary property or add an arbitrary event listener to an element in JSX?
1 reply 0 retweets 2 likes -
Replying to @justinfagnani
Ah - you mean like non-standard events or attributes? Yeah I understand what you’re saying now. It’s never come up for me, so I don’t know the details, but I at least understand you now. Thanks for clarifying.
1 reply 0 retweets 0 likes -
Replying to @AdamRackis
CustomEvents *are* standard events. "non standard" makes them sound obscure.
1 reply 0 retweets 6 likes -
Replying to @justinfagnani
Agree - I was inarticulate there.
@dan_abramov and@sebmarkbage hinted at event changes coming to React - I’m curious if those are part of the future plans?1 reply 0 retweets 0 likes
There are event changes happening, unclear if they're relevant thoughhttps://github.com/facebook/react/issues/15257 …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 