Mkdocs uses grayscale rendering for fonts compared to majority of the sites which use subpixel rendering about mkdocs HOT 7 CLOSED

Hopefully this gets merged asap and people update their shit, this shit makes everything blurry and painful to read

Please mind your language.

I will not mind my language when people fuck up things and refuse to admit they have fucked up things

from mkdocs.

@ryuukk Blocked.

from mkdocs.

I found the cause, i submitted a PR squidfunk/mkdocs-material#6916

Hopefully this gets merged asap and people update their shit, this shit makes everything blurry and painful to read

from mkdocs.

Hopefully this gets merged asap and people update their shit, this shit makes everything blurry and painful to read

Please mind your language.

from mkdocs.

@ryuukk Thanks for pointing me towards the *-font-smoothing options. I definitely agree with you - if a user has configured their preference for font rendering, what business do individual websites have overriding that preference and standing out like a sore thumb against the entire system?

I am in the opposite camp (grayscale forever!), and I'm guessing probably my browser doesn't support this setting, because I instantly snipe the christmasy-lit-up looking letters when subpixel rendering somehow sneaks into my system, but I've never observed it in Firefox.

And of course for this case, I don't notice if MkDocs themes set it to grayscale because that's what I already have. But I will always support removing any such overrides whenever possible :)

So yes, it is sad that the most used theme for MkDocs - "material" - now considers it a fundamental change to un-mess with the fonts.

As for MkDocs' built-in themes:

• The "mkdocs" theme never has any mentions of "font-smoothing".

• The "readthedocs" theme unfortunately inherits some instances of "font-smoothing". But weirdly, of any noticeable things, it is applied only to admonitions from what I observed, and otherwise it's applied only to tiny controls.

  (how do I know? my method of testing was:
  replace -webkit-font-smoothing:antialiased;
  with -webkit-font-smoothing:antialiased;font-family:"Comic Sans MS" !important)

  

So the original claim from the issue "Mkdocs (any mkdocs theme)" by @stojan97 is either wrong or simply a different claim than @ryuukk 's

Even more weirdly, @stojan97 links to Docusaurus as a "good" opposite example, but their website sets the exact same CSS as mkdocs-material! - -webkit-font-smoothing:antialiased - so this claim makes even less sense then.

But hopefully we can at least agree that MkDocs shouldn't start messing with font rendering in all themes.

from mkdocs.

@ryuukk whether you're right or wrong, that is not a way to speak to anyone. I invite you to read the code of conduct followed by MkDocs. Please try to maintain a respectful and constructive attitude when interacting with other people within the MkDocs community.

from mkdocs.

@stojan97 - Thanks for the report. ☺️
I don't think we'll treat this as an issue unless someone's invested enough to proactively deal with a pull request.

from mkdocs.