SoylentNews is people
SoylentNews
posted by
paulej72
on Sunday March 19 2017, @12:15PM
from the kill-one-bug-find-another-must-be-cockroaches dept.
from the kill-one-bug-find-another-must-be-cockroaches dept.
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:
- Comment titles now act to trigger actions as well as the buttons.
- New icons for the buttons that are bigger and spaced out a bit more.
- Removed extra spacing for some of the modes when buttons are hidden. (Still needs some more work, but much better than before.)
- Changed how we set states for hidden threads so that the individual comments are not set hidden as well. This will lessen the number of clicks needed to open a comment in this case.
- Flat comment mode will now show a comment's children when look at comment (cid is set).
- Temp fix for Content Security Policy eating CSS when not on https://soylentnews.org.
- Domain Tags now show in comments.
- Fixed broken messages when looking at them from messages.pl.
- Fixed for @user: shortcut links that would eat a character after the ":".
And here are the latest updates:
- Editor fixes: added new lines to story editor and fixed topic tree popup issue.
- Fix for black on black text boxes in Grayscale theme
- Added SVG icons for buttons and CSS fixes to enhance look.
- Mod Points now back to UTC 00:10.
- Add # of children to collapsed thread title.
- Fix comment details to bring in the correct data which broke email and journal links.
- Add time to collapsed comment title.
- Fix select all button in messages.pl.
- Redirect returns to correct article.pl page after moderating.
- Updated CSP to fix issues. We still need to search for some inline JS that may need to be purged or rewritten to work correctly.
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:
- FIXED: When viewing the list of messages you have received, the "Select All" checkbox has stopped working because we removed Javascript.
- There are still features of the old "Nested" display mode that are not reproduced in the new "Threaded-TOS" / "Threaded-TNG" display modes.
- TESTING ON DEV: Issues with Expand/Collapse comment tree versus Hide/Show comment tree. New expand all in tree button.
- MOSTLY FIXED: We are aware of issues with our (stricter) Comment Security Policy (CSP) support; especially accessing the site from TOR/Onion and from the deprecated https://www.soylentnews.org/ URL — one should use: https://soylentnews.org/ instead, but we are still trying to handle that automatically.
- Pagination and Redirects; there are known issues with implementation of the "&page=" parameter in the URL, especially when "&cid=" is also specified. For example, I have my page size set to 20 comments, someone else has the default of 100 comments, and I refer to a comment on my page 4, which is still on page 1 for the other person.
- In URLs, we currently use "&noupdate=" to toggle when the "*NEW*" flag and comment dimming take effect. has knock-on side effects that were not anticipated. Are planning to change to the reverse sense: "&update=", instead.
- Lost functionality during upgrade: Sort order by comment score.
- FIXED: User Journal link missing in details bar
- Pick sane default for AC mode and for Threshold/Breakthrough
- Some people are still having issues with previously-seen comments' dimming. Not so much that they are dimmed, but in how they are dimmed. Maybe dim the only the title? Maybe change the color?
- Spoiler tag needs to be triggered by text.
- Buttons on phones might still be too small since mobile browsers like to resize the text larger making everything else too small
- SOMEWHAT FIXED: Bug chrome/android phone when previewing comment messes up text size in edit box -- actually, slashboxes on RHS disappear after submitting comment or performing comment moderation. Resulting display area is much wider, so displayed font size is reduced by approximately 40%.
- FIXED: Possibly add date and time to collapsed comment title.
And here are the feature requests:
- Create moderation feedback as a modal dialog box via CSS (med term project).
- <code> tag support and styling.
- Edit after post (with limits).
- Markdown support for comments. (long term project)
- Button to reset all comments to unread (should be a quickie).
- New tags should not display for the first time a story is shown (may be a complicated issue to resolve).
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
It's raisins that make Post Raisin Bran so raisiny ...
(Score: 2, Interesting) by Anonymous Coward on Tuesday March 14 2017, @05:35PM (10 children)
Regarding Known Bug #10:
Some people are still having issues with previously-seen comments' dimming. Not so much that they are dimmed, but in how they are dimmed. Maybe dim the only the title? Maybe change the color?
I love the current system, and have used Stylish to dim comments even more (down to opacity:0.55). However, I find bright text or high contrast between text and background almost painful to read, and I'm aware that I'm an outlier. So I have two suggestions/requests:
Finally, my sincere thanks to the Dev Team, you people are awesome.
(Score: 2, Insightful) by pTamok on Tuesday March 14 2017, @05:53PM
I'll add my thanks to the Dev team.
It certainly helps considerably to have 'Meta' postings explaining why certain changes have been made. While I might dislike some of the changes, when I understand why they have been made, it makes them more palatable.
I am also very happy that some of the snazzy new features can be turned off in preferences. This is good. I know some people like the comment dimming. My first thought when I saw it happening was to be worried that my eyesight had suddenly got worse, and after my first panicked thought of macular degeneration striking, I was very glad to find it was intended user interface behaviour. And I was even happier to find I could turn it off!
I'm very grateful that you are putting in the time and trouble to keep the site ticking over. Well done.
(Score: 2) by wonkey_monkey on Tuesday March 14 2017, @06:58PM (2 children)
Perhaps just unbolding read comments would suffice.
systemd is Roko's Basilisk
(Score: 2) by paulej72 on Wednesday March 15 2017, @12:02AM (1 child)
Our old js based code had only one set of icons that were used on all themes. We had to style them so they always worked. To keep things simple. I have only created one set of the new icons.
I think we may need to create theme specific icons that fit better in terms of colors and contrast.
Team Leader for SN Development
(Score: 2) by wonkey_monkey on Wednesday March 15 2017, @04:49PM
I like the change from the single/double arrows to +/-. For some reason I've always found arrows ambiguous. Is a down arrow saying "click here to open the comment below" or is it saying "the comment below is already open; click here to close it?"
For some reason +/- doesn't have that ambiguity for me.
systemd is Roko's Basilisk
(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.