After reading /. for a while, Im experiencing a problem
with your page counters for moving through extended
discussions.
It doesnt work on my system!!
I might be going mad about this for nothing, but I
cannot find anywhere to alter this (I would like the
entire conversation rendering in one go, and already
have it set on maximum (100). I do realise the problems
from your end, but having stable page indexes prevents
this from being a problem.
When I reach the end of the current page, and am
reading a comment I expect the next page to continue
at the next comment.
What actually happens is it makes the next page, but
seems to just start again in the middle of the 1st page.
for Example:
Page1
Comment1
Comment11
Comment12
Comment2
Comment21
Comment3
Comment31
Comment32
Comment4
Comment5
[Click on the 2]
Page2
Comment3
Comment31
Comment32
Comment4
Comment5
Comment6
Comment7
...
The expected action should be:
Page2
Comment6
Comment7
...
Is this a bug, or am I simply not using my eyes?
If the problem is at your end, then I am prepared to
make some additional tests, or obtain specific
information as may be required.
If its something I can change in my settings, could you
please shed light onto where I would find the setting in
question.
Liquidcoooled (Gary)
Logged In: NO
I read mostly at -1 Nested and have seen this problem a lot.
When a comment thread gets very long and does not fit on a
page the first comment on the next page tends to be the top
level comment in that thread and not the next comment after
the one on the previous page.
The worst example of this I saw was when the first comment
provoked so many responses that the first 4 pages rendered
at -1 nested had exactly the same comments on them.
Example
page1
1
1.1
1.1.1
1.1.1.1
1.1.1.2
1.1.1.2.1
1.1.1.3
1.1.2
1.1.2.1
1.1.2.2
1.1.2.3
1.1.2.3.1
1.2
1.2.1
page 2
1
1.1
etc.
page 3
1
1.1
etc.
page 4
3
3.1
etc.
How can I get to read comments from the second top level
thread? Or even the comment 1.4 or 1.2.3 etc.
Logged In: YES
user_id=886129
It's a bug that I've seen ever since I started visiting /. a
few months ago. A good example would be "SCO Now Willfully
Violating the GPL" from Oct 31st, as there are over 1000
comments:
http://slashdot.org/article.pl?sid=03/10/31/1451233&mode=nested&tid=187&tid=88
At threshold -1, flat mode, oldest first (ignoring threads),
the last comment on page #1 is (#7358293), and it doesn't
show up on page 2. So that works properly, so long as no
comments are filtered out.
Change threshold to 0, now the last visible post on the 1st
page is (#7358339), however, this post is repeated on page 2
about 1/4 of the way down the page.
Change threshold to 3, the last visible post on page 1 now
appears again halfway down the 2nd page.
My configuration is to show 95 comments per page, but you
can get the same effect at other settings. The bug seems to
lie in the algorithm that figures out what the first post on
the next page should be when some posts are filtered.
Logged In: YES
user_id=975602
On my system, OSX 10.2.8/Safari, page 2 is exactly, or almost
identical to page 1. Page 3 has a few new comments at the
bottom, and you have to go to page 5 to see unread stuff. The
recent W2K source code story is a good example. Oh yeah, nested
at level 1. This bug filing is a little old; makes me think it may be
a browser issue?