Read It

by
in pipedot on (#3KF)
Ever revisit a popular story page and wish you could easily distinguish the new comments from the stuff you've already read? Well, now you can!

New comments are now shown in blue, while old comments are shown in gray. Simple enough, right?

Re: Nice! (Score: 2, Interesting)

by fatphil@pipedot.org on 2014-05-13 17:38 (#1JJ)

However, there's a bug :-(

If you reply to a post at the top of the thread, before reading the whole thread, then when you return to the thread after clicking "post", all those things you've not read are greyed out.

I presume this is just timestamp-based? If so, perhaps don't commit the "thread last rendered" timestamp until some affirmative thread-leaving action is performed. Posting a reply would not be classified as a thread-leaving action. This might require some significantly trickier smarts to implement than just the naive situation we have at the moment.

Simpler Workaround: middle-click the "reply" link to get it in a new tab, and then just close after posting.
Post Comment

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64
Fatal Error - sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.217.139] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null] - Pipedot
Fatal Error
sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.217.139] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null]
Subject
Comment