News for hackers. Stuff that matters.
Re:Firefox 63 – Tricks and Treats by jaimehrubiks on Tuesday October 23, 2018 @08:31PM (#18288698)
Doing this feels like creating a react component somehow, doesn't it?
Re:Firefox 63 – Tricks and Treats by pjmlp on Wednesday October 24, 2018 @04:41AM (#18290676)
Kind of, although last time I checked React devs were the only ones not keen in moving into Web Components, while everyone else is moving into that direction.
Re:Firefox 63 – Tricks and Treats by leetbulb on Wednesday October 24, 2018 @10:43AM (#18292819)
It looks like people are wrapping WebComponents with React, but isn't that the wrong direction? From what I understand, since React's rendering has been abstracted, we'd just need ReactWebComponents instead of ReactDOM, where the rendering engine directly utilizes WebComponents and its native Shadow DOM implementation.
Re:Firefox 63 – Tricks and Treats by pjmlp on Wednesday October 24, 2018 @11:41AM (#18293358)
Quite right.

I must admit that I am not a React fan though, and do favour vanilajs.

Re:Firefox 63 – Tricks and Treats by leetbulb on Wednesday October 24, 2018 @12:25AM (#18289723)
Yeah, and it's great! Can't wait for Edge and Safari support and further maturation.
Re:Firefox 63 – Tricks and Treats by alwillis on Wednesday October 24, 2018 @01:57AM (#18290043)
Apparently WebKit had this nearly two years ago: https://webkit.org/blog/7027/introducing-custom-elements/
Re:Firefox 63 – Tricks and Treats by AndreasGalster on Wednesday October 24, 2018 @01:41AM (#18289983)
Actually Safari has been supporting this for over a year already :) Edge is probably coming out this spring