Dev.SN

SoylentNews' Issues Addressed in Release: 2017.12

posted by Bytram on Thursday December 14 2017, @02:40PM   
from the early-Christmas-gift dept.

Bytram writes:

Here is a summary of the problems that have been reported against SoylentNews and that have been addressed in the release labelled: "December 2017"

• Pull Request: #414 addresses:

  • Issue: #279 "Add min karma for the journals slashbox"

    PROBLEM:
    Accounts signing up then posting commercial spam Journal entries in order to appear on most user's view of the main SN site, within the Most Recent Journal Entries box. Whilst offering zero other contribution to the community.

    SOLUTION:
    A. Most Recent Journal Entries only to be populated with Journal entries by accounts with a Karma > N. 5 to be the initial value for N (that would hide all currently seen Journal spam from view), but should be an easily tweaked parameter should we need to revisit this threshold).

    B. Addition of a link to "Unfiltered Most Recent Journal Entries" to be added to the bottom of the Most Recent Journal Entries rehashbox so users can easily compare the filtered to unfiltered lists.

    ADDENDUM:
    This change will need to be clearly announced and rationale explained. We will also need to monitor effectiveness in case spam accounts begin to farm Karma in order to route around this change.

• Pull Request: #420 addresses:

  • Issue: #410: Spoiler tag doesn't work on Journal comments.pl

    See:

    https://soylentnews.org/comments.pl?sid=22596
    vs.
    https://soylentnews.org/~takyon/journal/2762

    It seems to work fine for articles:

    https://soylentnews.org/comments.pl?sid=22588
    https://soylentnews.org/article.pl?sid=17/11/16/013234

  • Issue: #281: Request: increase size of submission/story notes

    It seems to be limited to 1024 characters. How about 8192 or 16384 characters?

    Don't accidentally delete the notes!

    Need to update stories and submissions tables to set the notes and comments columns to text (from varchar(1023). Then need to update all of the templates to change the maxsize attribute.

  • Issue: #309: Link to submission queue on side bar

    Appears as a link to "https://dev.soylentnews.org/submit.pl?op=list" with link text "Subs Queue"

  • Issue: #413: Margins of lists are sometimes non-existent despite use of line breaks

    https://soylentnews.org/comments.pl?noupdate=1&sid=22853&page=1&cid=604019#commentwrap

    The margin-top or especially margin-bottom of lists does not always work as expected. See the above comment. There should be a line break between "IV" and "I believe these moderations would be extremely popular."

    The spacing (margins) does not match what is seen in the "Preview Comment".

    https://dev.soylentnews.org/comments.pl?sid=1401

    Also <ol type="I"> is not implemented on dev.soylentnews.org

  • Issue: #402: Comments with no apparent subject using a unicode space

    Chromas used a unicode space or zero-width space character to make a comment with no apparent subject. When you get a Message about receiving the comment, the CID is not clickable like it normally would be.

    https://soylentnews.org/comments.pl?noupdate=1&sid=21276&page=1&cid=559159#commentwrap

---

Original Submission

• 20171222a - OL - Tests #0000 (Score: 2) by Bytram on Friday December 22 2017, @09:35AM

  by Bytram (4031) on Friday December 22 2017, @09:35AM (#31483) Journal

  Tests of ordered lists to address issue #413 [github.com].

  Mozilla's specs for ol [mozilla.org]:

  Note: This is a quick stab to get a feel at what works and how -- really should be broken up into sub-tests, but I knew that already... have to get ready to go to work but did not want to lose these, and wanted to make the results more generally available.

    This element includes the global attributes.
  
  compact
      This Boolean attribute hints that the list should be rendered in a compact style. The interpretation of this attribute depends on the user agent and it doesn't work in all browsers.
      Note: Do not use this attribute, as it has been deprecated: the <ol> element should be styled using CSS. To give an effect similar to the compact attribute, the CSS property line-height can be used with a value of 80%.
  
  reversed [HTML5]
      This Boolean attribute specifies that the items of the list are specified in reversed order.
  
  start [HTML5]
      This integer attribute specifies the start value for numbering the individual list items. Although the ordering type of list elements might be Roman numerals, such as XXXI, or letters, the value of start is always represented as a number. To start numbering elements from the letter "C", use <ol start="3">.
  
      Note: This attribute was deprecated in HTML4, but reintroduced in HTML5.
  
  type
      Indicates the numbering type:
  
          'a' indicates lowercase letters,
          'A' indicates uppercase letters,
          'i' indicates lowercase Roman numerals,
          'I' indicates uppercase Roman numerals,
          and '1' indicates numbers (default).
  
      The type set is used for the entire list unless a different type attribute is used within an enclosed <li> element.
      Note: This attribute was deprecated in HTML4, but reintroduced in HTML5. Unless the value of the list number matters (e.g. in legal or technical documents where items are to be referenced by their number/letter), the CSS list-style-type property should be used instead.

  Test using a variety of sequential and nested ordered lists (OLs):

    <p>Defaults with one LI:</p>
    <ol>
      <li>one</li>
    </ol>
  
    <p>Defaults with two LI:</p>
    <ol>
      <li>one</li>
      <li>two</li>
    </ol>
  
    <p>Defaults with three LI:</p>
    <ol>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Sequence of OL with defaults:</p>
    <ol>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
    <ol>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Trying different values of TYPE: 'a', 'A', 'i', 'I', '1'</p>
  
    <p>Single list with type='a'
    <ol type='a'>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Single list with type='A'
    <ol type='A'>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Single list with type='i'
    <ol type='i'>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Single list with type='I'
    <ol type='I'>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Single list with type='1'
    <ol type='1'>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Nested OL using defaults:</p>
  
    <ol>
      <ol>
        <li>one</li>
      </ol>
    </ol>
  
    <p>Nested list BEFORE first item:</p>
  
    <ol>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>
      <li>one</li>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Nested list AFTER first item:</p>
  
    <ol>
      <li>one</li>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>
      <li>two</li>
      <li>three</li>
    </ol>
  
    <p>Nested list AFTER second item:</p>
  
    <ol>
      <li>one</li>
      <li>two</li>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>
      <li>three</li>
    </ol>
  
    <p>Nested list AFTER third (last) item:</p>
    <ol>
      <li>one</li>
      <li>two</li>
      <li>three</li>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>
    </ol>

  Test using a variety of sequential and nested ordered lists (OLs):

  Defaults with one LI:

  1. one

  Defaults with two LI:

  1. one
  2. two

  Defaults with three LI:

  1. one
  2. two
  3. three

  Sequence of OL with defaults:

  1. one
  2. two
  3. three

  1. one
  2. two
  3. three

  Trying different values of TYPE: 'a', 'A', 'i', 'I', '1'

  Single list with type='a'

  1. one
  2. two
  3. three

  Single list with type='A'

  1. one
  2. two
  3. three

  Single list with type='i'

  1. one
  2. two
  3. three

  Single list with type='I'

  1. one
  2. two
  3. three

  Single list with type='1'

  1. one
  2. two
  3. three

  Nested OL using defaults:

  1. 1. one

  Nested list BEFORE first item:

  1. 1. one
     2. two
     3. three
  2. one
  3. two
  4. three

  Nested list AFTER first item:

  1. one
  2. 1. one
     2. two
     3. three
  3. two
  4. three

  Nested list AFTER second item:

  1. one
  2. two
  3. 1. one
     2. two
     3. three
  4. three

  Nested list AFTER third (last) item:

  1. one
  2. two
  3. three
  4. 1. one
     2. two
     3. three

  --
  A sig for when you want to see one

  Starting Score:	1		point
  Karma-Bonus Modifier		+1
  Total Score:		2