71–80 of 133 posts
Are these defaults part of Skia or Chromium, i.e. will all Skia dependents benefit from this change?
My overriding feeling after reading this is: displaying text is a key job of a web browser. A browser that showed no text would be useless. And yet, after learning that Chromium's text looked wrong on Windows (by far the most important platform for Edge and Chrome), it took 4 years for the Chromium and/or Edge teams to fix it. 4 years of user research? 3 years to respect the user's ClearType Tuner values? Being a reg…
Text didn't look bad. It just didn't look identical to the rest of the OS.
It's not obvious why that should be a blocker at all, rather than a low-priority inconsistency.
And for people who switch between devices all day long but use the same browser, you could even argue that it's more important for text rendering to be consistent in a browser across devices, rather than consistent within a device. I don't personally think that, but I can see why there might discussion over whether this is even an issue at all, much less a blocking one.
That's really great news. I always wondered why text rendering in Chrome looked so much worse than Firefox.
Is it my impression or text rendering on Windows is just worse than on other platforms?
On the other hand, back in Mac OS X Leopard, the OS lets you adjust the level of font smoothing. I preferred the strongest level of smoothing. Many designers hate that because it is akin to faux bold. I didn't like that Apple removed it in Snow Leopard. These days it hardly matters though.
It would be great if we could also go ahead and fix subpixel anti-aliasing for OLED screens. People have been been trying for years to get Microsoft's attention about this issue. [1] The subpixel layout of OLED screens is different than the the traditional layout, so text ends up looking pretty bad. Patching ClearType would be the first step to fixing this issue. I'm surprised that none of the display manufacturers h…
I have a 27" 1440p 3rd gen QD-OLED panel and while I can make out some fringing if I pay real close attention to black-on-white text, it's not noticeable in general usage. The 4k panels have such a high DPI that I can't see the fringing at all without a magnifying glass.
My overriding feeling after reading this is: displaying text is a key job of a web browser. A browser that showed no text would be useless. And yet, after learning that Chromium's text looked wrong on Windows (by far the most important platform for Edge and Chrome), it took 4 years for the Chromium and/or Edge teams to fix it. 4 years of user research? 3 years to respect the user's ClearType Tuner values? Being a reg…
> Being a regression from pre-Chromium Edge, this should have been a release blocker on Chromium-based Edge. Instead, text looked bad for 4 years. Text didn't look bad. It just didn't look identical to the rest of the OS. It's not obvious why that should be a blocker at all, rather than a low-priority inconsistency. And for people who switch between devices all day long but use the same browser, you could even argue…
Earlier quoted context omitted.
The Steam Hardware Survey samples the system when Steam is launched, not while a game is playing. For most users, Steam starts when they log in to the computer. I think the unfortunate reality is that a very large number of gamers are still using 1920x1080 as their everyday ordinary screen resolution for their primary display, though a few percent at least are probably on laptops small enough that 1920x1080 is somewh…
>The Steam Hardware Survey samples the system when Steam is launched, not while a game is playing Who's installing steam on their non-gaming computer?
My overriding feeling after reading this is: displaying text is a key job of a web browser. A browser that showed no text would be useless. And yet, after learning that Chromium's text looked wrong on Windows (by far the most important platform for Edge and Chrome), it took 4 years for the Chromium and/or Edge teams to fix it. 4 years of user research? 3 years to respect the user's ClearType Tuner values? Being a reg…
It would be great if we could also go ahead and fix subpixel anti-aliasing for OLED screens. People have been been trying for years to get Microsoft's attention about this issue. [1] The subpixel layout of OLED screens is different than the the traditional layout, so text ends up looking pretty bad. Patching ClearType would be the first step to fixing this issue. I'm surprised that none of the display manufacturers h…
My overriding feeling after reading this is: displaying text is a key job of a web browser. A browser that showed no text would be useless. And yet, after learning that Chromium's text looked wrong on Windows (by far the most important platform for Edge and Chrome), it took 4 years for the Chromium and/or Edge teams to fix it. 4 years of user research? 3 years to respect the user's ClearType Tuner values? Being a reg…
What about all the designers that used to handle this issue by tweaking their font weights, colors...? Changing a long standing issue with a lot of users will break things for some people (using edge, with an eyes for these details..)
As a web designer, you must accept that the browser is fundamentally not yours to control. It is an agent acting on behalf of the user, not on behalf of you.