So the Dev Team has been hard at work fixing up issues with with the 17_02 release. We compiled all of your comments from the 17_02 Meta stories into a large bug and feature request list. We have been working on getting these issues fixed as soon as we can.
You may have noticed some changes over the last week that went out to fix some issues, and we just released some more fixes today.
Here is a list of the major fixes since the last story:
And here are the latest updates:
Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode
Site Update - Taking a Breather
Outstanding Issues
So if you see any new bugs that you think are related to these changes, or just want to let us know about an ongoing issue, please feel free to comment below.
Here are the currently known bugs that we are working on:
And here are the feature requests:
(Score: 2) by andersjm on Tuesday March 14 2017, @07:46PM (5 children)
Perhaps you should dial down on the brightness or contrast of your monitor.
(Score: 0) by Anonymous Coward on Tuesday March 14 2017, @09:46PM
Perhaps you should dial down on the brightness or contrast of your monitor.
Brightness 30%, contrast 50%. Any lower and UIs, videos, and games start looking problematic :)
(Score: 2) by Magic Oddball on Wednesday March 15 2017, @10:47AM (3 children)
If it's the same problem I have, then that will only alleviate the problem plus make it harder to read the black text. It's pretty much a persistent variant of the photosensitivity that most people only experience with nasty hangovers or migraine headaches.
My usual solution is to use Stylish to rewrite the CSS on websites I visit regularly that force a white background or other color/contrast combos that hurt my eyes.
(Score: 3, Interesting) by andersjm on Wednesday March 15 2017, @09:41PM (1 child)
Sorry if I was being callous. A lot of people leave brightness and contrast at the factory setting, so it seemed like a good bet at the time.
In reality you are a victim of the web designer conspiracy: Your browser most likely has settings for foreground and background colour, and font, and a properly designed web page would use these user preferences for body text. Unfortunately there are no properly designed web pages these days; every single web designer in the last 20 years have failed in that task, deciding instead that they know better than you what the text you read should look like.
Perhaps SN could buck the trend? My suggestion would be a binary user setting, "respect the reader's font and colour preferences in body text", which when set would mean zero CSS styling on <p>, allowing your browser preferences to stand.
(Score: 2) by paulej72 on Thursday March 16 2017, @02:50PM
Also the reverse of this issue is what I hear most. That there is not enough contrast between the background and the foreground. This is one of the things I try to keep in mind when choosing colors for themes. I try not to get below 50% difference, like doing 40% gray on white, but doing 40% gray on black would be acceptable.
It is very hard to have one theme work for everyone, but I do think the Grayscale theme may be good for people who need lower contrast. And I do have the fix for that in testing, and it should go up this weekend, along with fixes for some of the other issues mentioned here.
Team Leader for SN Development
(Score: 2) by deimtee on Wednesday March 15 2017, @10:00PM
I have a similar issue with some high contrast themes. Have you tried the "Grayscale" theme in prefs? I found it the easiest on my eyes. It currently has a slight bug with almost black text on a black background when typing comments, but Paulej72 has said that it will be fixed later this week.
If you cough while drinking cheap red wine it really cleans out your sinuses.