Powers-that-lurk:
Tried to incorporate an <ol> list in a post today, but it failed to work properly. I wrote:
<ol type="A">
<li>Thing</li>
<li>Another thing</li>
</ol>
What I got:
1. Thing
2. Another thing
What I should have gotten:
A. Thing
B. Another thing
I request that you fix the tag so that this works. I presume the original HTML tag construct is preferable to allowing limited CSS styles, but if that was also available, that'd be okay too. I'm also making the assumption that CSS styles are not currently available, which I suppose could be wrong. :)
If you're in there making <ol> work anyway, probably should also address "start=X" and "reversed" as well.
One of the things I really like about Soylent is that it works better than That Other Place. More, please.
Thanks.
(Score: 0) by Anonymous Coward on Sunday October 08 2017, @04:10AM (11 children)
You could partake in the necessary damage to your brain so that you too are fluent enough in perl to fix it too.
In all seriousness, maybe you should add something at the bug tracker [github.com]? Judging by the HTML of what I get back, the code strips out the "type" attribute (which, in general, is probably a good idea for attributes). May not be that hard to fix, depending on how the filter code works.
(Score: 2) by The Mighty Buzzard on Sunday October 08 2017, @10:54AM (10 children)
Appreciate the recruiting but it's not a perl thing in this case. Attributes for html tags have to be specifically allowed within the database, which I just took care of.
Unfortunately it appears list-style for ol li tags within commentBodys is also specifically stated as decimal in our css for some reason. I've put a temporary fix in but it'll also need to be updated in the source tree.
My rights don't end where your fear begins.
(Score: 2) by The Mighty Buzzard on Sunday October 08 2017, @10:55AM
Odd, it appeared fine in preview...
My rights don't end where your fear begins.
(Score: 2) by The Mighty Buzzard on Sunday October 08 2017, @11:04AM (6 children)
There, that's better.
My rights don't end where your fear begins.
(Score: 2) by FakeBeldin on Sunday October 08 2017, @11:15AM (2 children)
Just fyi: It's showing up as "1. First", "2. Second" here, even though the source has "type='A'".
(Score: 4, Informative) by The Mighty Buzzard on Sunday October 08 2017, @11:36AM (1 child)
Almost certainly a cached CSS file. Should clear up eventually or you can force refresh. Double checked in six browsers and I get A/B in all of them.
My rights don't end where your fear begins.
(Score: 2) by FakeBeldin on Monday October 09 2017, @11:43AM
Thanks, force-refresh solved the issue.
Thanks for testing extensively, despite the likelihood of PEBKAC.
(Score: 3, Informative) by takyon on Sunday October 08 2017, @08:18PM (2 children)
Wow, I get to add a new button (A. List) to my extension.
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 0) by Anonymous Coward on Monday October 09 2017, @01:57AM (1 child)
You have a SoylentNews extension for browsers? Do tell! Chromium or Firefox?
(Score: 2) by takyon on Monday October 09 2017, @03:14AM
It's a userscript so it works on both.
https://soylentnews.org/~takyon/journal/2300 [soylentnews.org]
It adds all of the features described here: https://soylentnews.org/comments.pl?noupdate=1&sid=12471&cid=312966#commentwrap [soylentnews.org]
as well as a spoiler button, title case button for journals, and a button that cycles through *New* comments.
For the next version, I'll probably add this new ordered list button, and more symbol crap, like the country code flags that realDonaldTrump [soylentnews.org] uses. I'll add a couple of exceptions to the title case button, like "iPhone" instead of "IPhone" which has been an issue forever. And that's all I can think of because it is pretty complete.
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 2) by The Mighty Buzzard on Sunday October 08 2017, @11:09AM (1 child)
Mind you, this fix is only for comments.
My rights don't end where your fear begins.
(Score: 2) by fyngyrz on Thursday October 19 2017, @11:29PM
Thanks. :)