![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Visually mark new comments since last reload
Title:
Visually mark new comments since last reload
Area:
Comments
Summary:
When you reload the page, any comments that have been posted since you last loaded the page would be marked as visually distinct and new.
Description:
This is about the only thing I really like about LJ's redesign, personally, so I thought I'd suggest it over here. It could be done with either a hardcoded visual thing like LJ's, where a little yellow new comment button shows up next to new comments, or something that can be styled with CSS to be a dot or a different header color or whatever, that would just become part of the layout and people can choose to maximize or minimize how much it stands out.
It's especially helpful in very fast-moving posts where you want/need to track what everyone is saying, but need more context for each thread than tracking and only seeing what the immediately previous comment said with the newest comment, rather than seeing the last 10 comments in a straight row. I play a game on occasion where 5-10 people can make a hundred comments in an hour all on pretty much the same topic and you have to try to be following them all, and the last time I played it was oh my god so much easier with that feature. But it's the kind of thing that seems like it would be useful in almost any discussion you want to follow, but don't quite want to track the post for whatever reason.
This suggestion:
Should be implemented as-is.
55 (59.8%)
Should be implemented with changes. (please comment)
6 (6.5%)
Shouldn't be implemented.
5 (5.4%)
(I have no opinion)
26 (28.3%)
(Other: please comment)
0 (0.0%)
no subject
You can do this now by using the "flat" link on the comment page - it de-threads all comments and lists them in strict order of posting, so you can read, oh, the last 10 comments in a straight row. It's not perfect (it hides any structure with the threading, except what's revealed by subject lines) but I thought I'd mention it in case you didn't know - it's completely changed the way I follow large discussions.
no subject
no subject
As far as back-end goes, there would probably need to be some sort of "new-since-last-visit-from-this-user" flag property attached to the comment, which the stylesheet would then check for. Thus the "display this labeled as unread" behavior would be easy to change in one place if studying determined that the display wasn't working for some reason (without having to rebuild the whole back end) and it would be also available for S2-styled comment views in every style without having to do a lot of shenanigans.
no subject
no subject
How it works is, when the reading page is first loaded, the back-end counts the current comments and puts a ?nc=17 on the end of the comments link for an entry that has 17 comments. Meanwhile, your browser knows that you've visited the link. When you reload your reading page again, it's gone up to 18 comments, and Dreamwidth serves a ?nc=18 link, and your browser doesn't recognize that link, so it uses the "hey! new link!" color. Since all Dreamwidth is doing is giving a link that says how many comments are in it, it doesn't actually keep track of whether you've visited or not already.
This falls down when say you're on the page and it's now got 18 comments, and you go ahead and leave 4 more replies, so now it's up to 22 comments. Meanwhile, you haven't actually loaded the ?nc=22 link, you've just been on the entry page. So when you come to the ?nc=22 link on your reading page again, the link's showing unread, but you've already seen the other 4 comments.
I don't think there's a way to make your browser track what separate on-page objects you've seen outside of loading single-comment links for them all.
no subject
no subject
no subject
So not exactly what some are looking for.
no subject
no subject
no subject
no subject
no subject
Using CSS would be ideal - then people could choose to have it do nothing, or mark new comments, or even entirely hide the old comments.
(I was once working on an implementation that allowed for manual mark-as-read, mark-as-unread, mark-all-as-read, etc; and was working up to add functionality so that scrolling past an item would automagically count as marking-as-read. I can't remember how I planned to do that, alas. Probably with much trial-and-error and swearing.)
no subject
no subject
no subject
no subject
no subject
1.) I want an opt-in; I feel like this would be distracting in RP, and if it adds to page load time at all I wouldn't be interested.
2.) "Visual" distinction is the wrong way to look at it. This would, if anything, be even more useful for users who can't scan an entry visually. :|a I don't know a lot about screen readers, but if we add something to indicate new comments, I think it should be something that screen readers could identify and tab between. "New comments!" would be announced via the screen reader, and then the screen reader would go straight from one to the next, skipping all the old comments unless the user would rather read the entire post.
Just food for thought.
no subject
But I wouldn't turn a similar thing on in dw if it was only visually-indicated by color or with a dot or whatever - I use subdued colors for a reason! Plus I'd like it to be something I could search for to quickly run through all the new comments in situ in their threads; using the mark-new-comments script, I can just crtl-f the all-caps "NEW" and quickly shuffle through all the new comments, and I couldn't do that with a visual indication. I can definitely see the uses of the visual-only notification, though, for other people, so maybe it would work better if it could be coded with the journal layout to be either text or icons/images, the way some other journal features already are?
no subject
no subject
- collapse old and expand new comments
- show only new comments
- add a visual identifier: mark the text in a different colour, on a different background, display an icon next to it - all the CSS fun
- you could even add 'NEW: in front of the subject line. (Would that work for screen reader users?)
-... pprobaby more things I can't think of right now.
I dislike the LJ implementation - I'm lost in the white space and my brain isn't parsing the yellow blocks as meaningful information, particularly as they're too far down - it's information I'd expect in the header of a comment, not what appears to be its body.
no subject
I might think with or near the timestamp?
no subject
no subject
no subject
no subject