Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:2

Changing comment display?

posted by Krow on 02:08 AM September 30th, 2002   Printer-friendly   Email story
I have noticed a surprising behavior in slashcoded sites. It seems like a bug to me, but as a lay user I may be missing the Big Picture of why one would want things this way.

Specifically, I was surprised to find that when changing the comment display parameters (e.g., threshold, nesting, ordering) of a displayed article, the resulting page does not display the original article; the comments are shown as requested, but the initial paragraph is not drawn. I first noticed this switching to a nested display on a recent Slashdot article, but some quick testing revealed that the behavior is consistent across various sites and browsers. Clearly, this is a systemic condition.

Is this a deliberate choice? Is there some reason to prefer this approach to one that allows a user to display the entire article with the comments organized as he/she chooses? From where I sit, I don't see why one would, but I was interested to hear what the community thought before submitting a bug report/patch. What do you think?

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.
More | Login
Loading... please wait.
  • I've noticed too, and I don't like it either. Haven't looked into it yet, except that I noticed that the new page without the article is displayed from instead of

    What's the slash{code,dot} crew saying?


    -- []: YAGSS - yet another German slash si

  • I think this is deliberate.

    From my point of view, anyone who gets that far has already read the story. So if they change their comment-view, why would they want the story's text to take up screen space.

    I wonder what the ratio is for people who are logged in, and have changed their comment settings - how often do they temporarily change their view when reading a story??

    Me personally, not all that often. But it depends on the story, and the site's layout.

    lottadot []
    • Occasionally. I'm set to threshold 1, threaded, highest first, show at +3. If I'm reading a story that is really interesting for some reason, I'll change to nested view so I don't miss anything. And if I've got mod points (and reading a story I'm knowledgable enough about to moderate well), I'll switch to nested, newest first.

      But even those times, I sometimes find I want to re-read something in the original story. It's not too hard to back up once, then forward once, though, so I don't worry about it.

      Constitutionally Correct [] ⇐
      • sometimes find I want to re-read something in the original story

        I find myself doing the same thing sometimes. Other things being equal, I would prefer to have the story shown.

        Another reason I would like to be able to do this that sometimes I like to "prepackage" a link to an interesting page to mail to somebody. It's nice to be able to set the comment-display options to highlight relevant posts (especially for non-slash saavy folks) while still showing them the original article (remember, the recipient

    • I'm sure you're right about deciding not to redisplay the main article to avoid repetition. I am less clear, however, on the real benefit to that; given the numerous posts on many articles, whatever efficiencies may be gained are lost in the noise of the endless scrolling required to view the comments.

      In other words, you wind up trading something that you MIGHT want for something that doesn't do you any good anyway. Personally, I'd say it would be better at least to have the option to preserve the article