Last active
February 2, 2021 20:42
-
-
Save illixion/08c9314f660a195c93286fdb5e944cce to your computer and use it in GitHub Desktop.
Removes Google Sans from the search results page
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// ==UserScript== | |
// @name UnSansify Google Search | |
// @namespace http://catto.io/ | |
// @version 1.1 | |
// @description Remove Google Sans font from the search results page | |
// @author Manual | |
// @match www.google.com/* | |
// @match google.com/* | |
// @grant GM_addStyle | |
// ==/UserScript== | |
GM_addStyle('#res h3, #botstuff h3 { font-family: arial,sans-serif !important; };') |
I've implemented a more reliable selector, can you please check that this works for you? I'd check myself, but I didn't get this A/B test on any of my devices.
Yes, that worked! It still doesn't work with the spacing in the header with ViolentMonkey, but the new code applies and looks right now with my edited header. Thanks!
For reference, here's the code that is working for me:
// ==UserScript==
// @name UnSansify Google Search
// @namespace http://catto.io/
// @version 1.1
// @description Remove Google Sans font from the search results page
// @author Manual
// @include http*://*.google.com/search*
// @grant GM_addStyle
// ==/UserScript==
GM_addStyle('#res h3, #botstuff h3 { font-family: arial,sans-serif !important; };')
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does this fix work for you? It's not working for me with ViolentMonkey in Firefox Developer Edition 85.0b9 64-bit for Linux.
At first, it didn't even match (so I couldn't load the script on the Google search results page), but I modified it to remove the extra spacing between the @stuff and the values, and then it matched at least, but it doesn't seem to change the font.
Is there a working fix for the change that was implemented by Google yesterday?