Hacker News new | past | comments | ask | show | jobs | submit login

I don't know the exact reason why, but it probably has to do with the fact that Edge and Firefox both use Direct2D for rendering and DirectWrite for text, while Chrome uses Skia (which can call into DirectWrite or GDI for text rendering I believe, but may not do so in the exact same way).



Skia is now the default on firefox/windows when direct2d isn't available.

http://techdows.com/2016/10/firefox-52-skia-enabled-by-defau...

What does that actually means in practice? I'm guessing the only time you actually get skia is when running in a pretty old hypervisor environment or on a server/BMC without hardware acceleration.

Which IMHO, having your application _LOOK_ different depending on hardware acceleration capabilities is sorta stupid.


> Which IMHO, having your application _LOOK_ different depending on hardware acceleration capabilities is sorta stupid.

Which is one of the reasons I transitioned from liking Web back into loving native development (there are plenty of other reasons though).

Doing discussions with customers about pixel differences across browsers, specially if it is the same browser on different OSes, is anything but fun.

That and the request for features and behaviors only possible in native UIs.


Should file a bug, though.


direct2d ? is that a thing on linux ?


No. Firefox uses skia on both Linux and macOS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: