Firefox 63 – Tricks and Treats | Hacker News Reader

Firefox 63 – Tricks and Treats

hacks.mozilla.org

49 pointsfeross11 comments

> After a rather long gestation, I’m pleased to announce that support for modern Web Components APIs has shipped in Firefox!

Finally, they are here! Great work.

Is one of the tricks and treats to enable forced video autoplay and remove the option to turn it off?

F you, and your trick and treats.

Love the entertainment & humor factor of the release notes. The 'very fancy' comment in the custom component's italics declaration for whatever reason slays me.

Seeing the font feature reminded me of a recent web design I did that loaded a custom local font. Anyone know why Webkit and Blink browsers differ so much with local font rendering? Matching designs was a nightmare in all major browsers and OSs, and that genuinely surprised me for frontend development in 2018. Why are major browsers differing on this still?

Not everybody agrees on the best way to draw text (some people like it blurry, others like it higher contrast), so I think the target users may matter to some level. It also varies by OS, and the OS even have options to let users influence it in some way.

Have you also noticed how even color rendering varies by browser? This is less intuitive...

Doing this feels like creating a react component somehow, doesn't it?

Yeah, and it's great! Can't wait for Edge and Safari support and further maturation.

Actually Safari has been supporting this for over a year already :) Edge is probably coming out this spring

Apparently WebKit had this nearly two years ago: https://webkit.org/blog/7027/introducing-custom-elements/

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.

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.

Quite right.

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

Reply on news.ycombinator.com