From 62d22f3277a3c4a7cd0b74b6ffe1bfc2e5775ed3 Mon Sep 17 00:00:00 2001 From: James Nord Date: Tue, 5 Dec 2023 06:27:23 +0000 Subject: [PATCH] do not specify anti-aliasing (#8689) specifying the anti-aliasing implies we know better than the browser (we don't). Specifiying this globally prevents the use of sub-pixel anti-aliasing where it is available and the browsers text rendering engines are these days pretty much fantastic that they should not need these hacks. and for good measure - here is an article from 10 years ago https://usabilitypost.com/2012/11/05/stop-fixing-font-smoothing/ and the mozilla doc saying do not use it on a public facing web site. https://developer.mozilla.org/en-US/docs/Web/CSS/font-smooth --- war/src/main/scss/base/_core.scss | 2 -- 1 file changed, 2 deletions(-) diff --git a/war/src/main/scss/base/_core.scss b/war/src/main/scss/base/_core.scss index 65541349fa80..ad90d35e8f55 100644 --- a/war/src/main/scss/base/_core.scss +++ b/war/src/main/scss/base/_core.scss @@ -1,8 +1,6 @@ html { height: 100%; box-sizing: border-box; - -webkit-font-smoothing: antialiased; - -moz-osx-font-smoothing: grayscale; -webkit-tap-highlight-color: transparent; color: var(--text-color); }