You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

dbaupp comments on [Website usability] Scroll to new comments (v0.3) - Less Wrong Discussion

13 Post author: dbaupp 08 August 2011 02:08PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (10)

You are viewing a single comment's thread. Show more comments above.

Comment author: dbaupp 09 August 2011 09:28:37AM 0 points [-]

Hmmm, I have an tiny idea what might be happening, but I haven't been able to reproduce it yet, so I'm unwilling to dive in and change things.

If that bug occurs to you (or anyone else) again, could you post a link to the specific comment(s) it occurs on? Thanks!

Comment author: Oscar_Cunningham 09 August 2011 12:31:47PM *  0 points [-]

I accessed this post while it had 27 comments. For me, they were all unread. The "next" button failed to do anything when I was on this comment (i.e. when the top of my screen was aligned with the top of that comment).

Pressing the "prev" button did nothing when the top of my screen was aligned with these comments: http://lesswrong.com/lw/70c/why_are_certain_trends_so_precisely_exponential/4mce

http://lesswrong.com/lw/70c/why_are_certain_trends_so_precisely_exponential/4mcf

http://lesswrong.com/lw/70c/why_are_certain_trends_so_precisely_exponential/4mcc

http://lesswrong.com/lw/70c/why_are_certain_trends_so_precisely_exponential/4mcd

http://lesswrong.com/lw/70c/why_are_certain_trends_so_precisely_exponential/4men

Comment author: dbaupp 09 August 2011 01:26:07PM *  0 points [-]

Thank you for that! Unfortunately, I can't reproduce your bug (and it's not what I thought it might be): I went through and added the "new comment" marker to those comments and their children, to try to simulate the circumstances, but everything worked fine for me. I'll update the script to include some logging (EDIT: done).

Has it happened on any other pages?

Comment author: Oscar_Cunningham 09 August 2011 02:23:41PM 1 point [-]

Aha! The problem is at my end, I've been viewing LessWrong zoomed-in slightly. Resetting to the default level of zoom prevents the error from happening.

Comment author: dbaupp 09 August 2011 03:01:22PM 0 points [-]

Nice! Thanks for the effort nonetheless.