Font Fuzziness after Purple Rain Update?
Back on January 22nd a number of users reported that on lower resolution screens of Windows PCs they were seeing some fuzziness in the font. Anti-Aliasing to use the technical term. We're trying to tr...
Forum Discussion
I believe I'm still seeing the issue--see how in the screenshot below, it's hard to distinguish the dot on the "i" in "Fields"?
Does this warrant opening a support case? I can certainly do so. Thanks.
Does this warrant opening a support case? I can certainly do so. Thanks.
- I think the font is Gibson-SemiBold - looks better with Gibson-Regular
- Well you could use the same Service Worker in my demo to immediately patch it to your liking faster than QuickBase will implement a fix.
https://community.quickbase.com/quickbase/topics/shes-a-rainbow - I'm very intrigued by your Service Worker stuff, but it's a bit over my head at this point. :)
- Well live and learn. Apparently my Service Worker broke because the release value was changed sooner than I though:
OLD
https://assets.quickbasecdn.net/res/873e615-1340/css/themes/classic/nav.css
New 2/1/2018
https://assets.quickbasecdn.net/res/873e615-1493/css/themes/classic/nav.css
It is easy enough the fix this but what I was trying to do at the moment was substitute the font on the third table to Comic Sans MS with this simple code:var respModified = resp.replace(/74489D/g, "95ED64").replace(/Gibson-SemiBold/g, "Comic Sans MS");
So if you revisit the application and re-register the Service Workers you will now see Arial on the third table:
UPDATE : changed to Gibson-SemiBold to Comic Sans MS for easier recognition.
https://haversineconsulting.quickbase.com/db/bne59biqr
Nothing surprising but it will probably take a few iterations to determine the best practices.
