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: 1) by DavePolaschek on Tuesday March 14 2017, @03:12PM (5 children)
The tags have links like <a href="//soylentnews.org/meta/search.pl?tid=8" class="topic2">Soylent</a> but the href isn't valid (no https: in it), so the link isn't clickable, so I am sad.
Not sure it it's a pre-existing problem or not.
(Score: 0) by Anonymous Coward on Tuesday March 14 2017, @04:24PM
For me they work just fine. And I always thought the browser was supposed to auto-fill the missing initial part anyway (so the omission of the protocol actually means that the link works on both http and https, leading you to the same type of protocol for the target as the one used for the current page), which is exactly what Firefox seems to do.
(Score: 3, Informative) by NCommander on Tuesday March 14 2017, @04:54PM (2 children)
a href=// is valid by spec, it means use the same protocol as this page was loaded on. It was a holdover from when we supported both HTTP and HTTPS before fully switching over to the later. Which browser is choking? Those links work right in both Chrome and Firefox. The themes haven't been edited because for dev systems, HTTPS can be a headache.
Still always moving
(Score: 1) by DavePolaschek on Tuesday March 14 2017, @06:35PM (1 child)
I'm using latest Safari (10.0.3)on Mac 10.12.3
(Score: 1, Insightful) by Anonymous Coward on Wednesday March 15 2017, @03:32PM
Then maybe you should file a bug report for Safari.
(Score: 3, Interesting) by The Mighty Buzzard on Wednesday March 15 2017, @03:56PM
That's a valid href value. The protocol is supposed to be matched by the browser to whatever protocol you got to the page with. Browser bug on your end.
My rights don't end where your fear begins.