Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Slashdot.org

Journal _xeno_'s Journal: Slashdot 2.2 - It ate my preferences!

Bah. I just posted my first comment to Slashdot while it was using 2.2, and I discovered - much to my horror - that my choice of "HTML Formatted" had been changed to Plain Old Text. Obviously I missed this when previewing it, but the ramifications were that:
  1. Slashdot changed my newlines into <BR>s. And made my paragraphs look really funny as a result. This might explain all the recent posts with the three-space-paragraphs - people write:

    <p>
    Paragraph 1.
    </p>
    <p>
    Paragraph 2.
    </p>

    Which should be rendered as:

    Paragraph 1.

    Paragraph 2.

    But gets bastardized as:

    Paragraph 1.

    Paragraph 2.

  2. Apparently, Plain Old Text doesn't really mean it, since my links came through fine. Although I find that [domain.com] really annoying (found the pref though, it's in Comments like it should be). I think Plain Old Text should be changed to Extrans, with the current Plain Old Text (format paragraphs for me) being replaced with some new name...

It also completely screwed up my Slashboxes - I got to have some fun moving them around to the way they were. I tried to come up with an easier way to do that, but it involves JavaScript (the horrors), and so probably wouldn't be accepted... I might wanna try and play around with Slashcode and create a patch for the fun of it anyway.

That and the "renest highly rated parents" is nice, except that it becomes much harder to read the comment they were replying to since the Parent link now links to the parent comment that it was renested to. I should see if unchecking that option fixes that in Nested mode.

This discussion has been archived. No new comments can be posted.

Slashdot 2.2 - It ate my preferences!

Comments Filter:

One small step for man, one giant stumble for mankind.

Working...