Skip to main content
Super User

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

Sorry, this is no answer, as the question includes no question ;)

I try to avoid anti-aliased fonts wherever possible as I second the opinion, that these "hurt eyes and damage eyesight".

The disadvantage is that a lot of web pages look ugly, because fonts are nowadays designed to be displayed anti-aliased only. Unfortunately this now also applies to SU (and the other StackExchange sites):

enter image description here

For sites I'm using on a regular basis I employ a user css to work around these font issues. For the SU site this works only partial... the reason is reveled by a look into SU's all.css:

font-family:'Helvetica Neue',Helvetica,Arial,sans-serif !important

This !important statement renders my attempts with a custom css useless.

Ironically, a gold-badge answer on SOgold-badge answer on SO clearly states:

Yes, !important is bad practice. !important was initially designed to help people with visual impairments overwrite the style sheets of websites.

So finally I'd like to ask why are in total 164 (as of now) !important statements used in the new style sheet? Shouldn't the StackExchange sites serve as a shining example?

Sorry, this is no answer, as the question includes no question ;)

I try to avoid anti-aliased fonts wherever possible as I second the opinion, that these "hurt eyes and damage eyesight".

The disadvantage is that a lot of web pages look ugly, because fonts are nowadays designed to be displayed anti-aliased only. Unfortunately this now also applies to SU (and the other StackExchange sites):

enter image description here

For sites I'm using on a regular basis I employ a user css to work around these font issues. For the SU site this works only partial... the reason is reveled by a look into SU's all.css:

font-family:'Helvetica Neue',Helvetica,Arial,sans-serif !important

This !important statement renders my attempts with a custom css useless.

Ironically, a gold-badge answer on SO clearly states:

Yes, !important is bad practice. !important was initially designed to help people with visual impairments overwrite the style sheets of websites.

So finally I'd like to ask why are in total 164 (as of now) !important statements used in the new style sheet? Shouldn't the StackExchange sites serve as a shining example?

Sorry, this is no answer, as the question includes no question ;)

I try to avoid anti-aliased fonts wherever possible as I second the opinion, that these "hurt eyes and damage eyesight".

The disadvantage is that a lot of web pages look ugly, because fonts are nowadays designed to be displayed anti-aliased only. Unfortunately this now also applies to SU (and the other StackExchange sites):

enter image description here

For sites I'm using on a regular basis I employ a user css to work around these font issues. For the SU site this works only partial... the reason is reveled by a look into SU's all.css:

font-family:'Helvetica Neue',Helvetica,Arial,sans-serif !important

This !important statement renders my attempts with a custom css useless.

Ironically, a gold-badge answer on SO clearly states:

Yes, !important is bad practice. !important was initially designed to help people with visual impairments overwrite the style sheets of websites.

So finally I'd like to ask why are in total 164 (as of now) !important statements used in the new style sheet? Shouldn't the StackExchange sites serve as a shining example?

Source Link
mpy
mpy
  • 28.4k
  • 11
  • 8

Sorry, this is no answer, as the question includes no question ;)

I try to avoid anti-aliased fonts wherever possible as I second the opinion, that these "hurt eyes and damage eyesight".

The disadvantage is that a lot of web pages look ugly, because fonts are nowadays designed to be displayed anti-aliased only. Unfortunately this now also applies to SU (and the other StackExchange sites):

enter image description here

For sites I'm using on a regular basis I employ a user css to work around these font issues. For the SU site this works only partial... the reason is reveled by a look into SU's all.css:

font-family:'Helvetica Neue',Helvetica,Arial,sans-serif !important

This !important statement renders my attempts with a custom css useless.

Ironically, a gold-badge answer on SO clearly states:

Yes, !important is bad practice. !important was initially designed to help people with visual impairments overwrite the style sheets of websites.

So finally I'd like to ask why are in total 164 (as of now) !important statements used in the new style sheet? Shouldn't the StackExchange sites serve as a shining example?