Firefox 63 – Tricks and Treats

Posted by feross on Tuesday October 23, 2018 @04:18PM
from the hacks.mozilla.org dept.

https://hacks.mozilla.org/2018/10/firefox-63-tricks-and-treats/

( 11 comments | 49 points | on HN )

Re:Firefox 63 – Tricks and Treats by pjmlp on Wednesday October 24, 2018 @04:40AM (#18290665)

> 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.

[ Parent | on HN ]

Re:Firefox 63 – Tricks and Treats by mancerayder on Friday November 02, 2018 @09:11PM (#18368057)

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.

[ Parent | on HN ]

Re:Firefox 63 – Tricks and Treats by zschuessler on Tuesday October 23, 2018 @08:41PM (#18288758)

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?

[ Parent | on HN ]

Re:Firefox 63 – Tricks and Treats by zeroimpl on Tuesday October 23, 2018 @11:17PM (#18289430)

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...

[ Parent | on HN ]

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?

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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/

[ Parent | on HN ]

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

[ Parent | on HN ]