= 27d567bc2d48d9f40e9ccc20ea370b15)
Oscar_Cunningham comments on [Website usability] Scroll to new comments (v0.3) - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (10)
Awesome. Thank you.
Bug report: The next button doesn't always work. I can't pin down exactly what circumstances cause this but it seems to happen only if the comment I'm currently on has no children.
I using Firefox 5 on Windows 7, and have comments sorted by "Old".
Thanks!
How does it not work? e.g. doesn't do anything, or scrolls to a random spot.
Doesn't do anything.
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!
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
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?
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.
Nice! Thanks for the effort nonetheless.