4 ms·
This isn't true https://facebook.github.io/react/docs/web-components.html https://facebook.github.io/react/docs/web-components.html
by peterhunt 9y ago
This isn't true https://facebook.github.io/react/docs/web-components.html https://facebook.github.io/react/docs/web-components.html
- dmitriid 9y agoIt's partly true, see https://custom-elements-everywhere.com https://custom-elements-everywhere.com and linked issues. The main problem: when the framework makes the developer decide whether to pass attributes or properties to Custom Elements, it's mostly ok. The framework should also allow binding any events (which cna be named as onEvent, or on-event or...) Frameworks that are trying to be clever and hide the complexities of DOM behind proper APIs, and that implement their own event systems suffer greatly because DOM APIs and WebComponent APIs are a pile of steaming crap.
- allover 9y agoThe site you linked to is about frameworks 'playing well with' custom elements. It says nothing to the assertion about React moving to web components. Also it is not helpful to call standards 'a pile of steaming crap' without backing that up with something substantive, examples/alternatives etc.