Stories
Slash Boxes
Comments

SoylentNews is people

posted by on Monday March 06 2017, @10:59PM   Printer-friendly
from the post-bills-here dept.

Okay, we've all had our weekends and I at least am ready to jump back onto the coding horse. Refresh my memory of what we still have that's either properly broken or is otherwise behaving in an entirely unsatisfactory manner. I think Flat-mode links to individual comments are still broken. I know we need to replace the "noupdate" behavior with explicit "update" behavior. I'm thinking I can get the colors on "*NEW*" comments' subject bars brightened up so that you can ditch dimming and still have easy visual feedback if you like fairly quickly. I'm considering (nearly (can't do "N replies below Threshold)) precisely replicating Nested and adapting the old javascript to it if you care to run it. But what am I forgetting?

Discussion to a minimum here, please, so it doesn't distract from having an all-in-one-place list of things from this release that still need addressed.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by martyb on Tuesday March 07 2017, @01:53PM (2 children)

    by martyb (76) Subscriber Badge on Tuesday March 07 2017, @01:53PM (#476000) Journal

    The *NEW* marker only doesn't make sense for the first time I open the comments page of a story (that is, all the comments are new).

    This one bothers me, as well. When I know this is the first time I am reading a story, all the NEW flags are distracting. OTOH, there are times when I (being human) forgot that I had read a story before and only realize this when I start reading the comments. That said, the former occurs far more often than the latter, so I would appreciate suppressing the new comment indicator on my first read of a story.

    Separately, the NEW text indicator is presented in a larger font than the rest of the headline text on my home system (Firebug says: font size: 16px vs. 13.6px) as it is inherited from the <H4> containing it where as the rest of the headline seems to have a span and custom class around it. Maybe add a separate class just for the text of the NEW comment indicator? Maybe something like this:

    <span class="comment_new_flag">*NEW*</span>

    I have a working ability with CSS but it is not my strong suit... others might have better suggestion(s).

    --
    Wit is intellect, dancing.
    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 3, Informative) by mechanicjay on Tuesday March 07 2017, @05:17PM (1 child)

    I got around this by turning off the *NEW* flag. I left the comment dimming setting on. It's actually been kind of amazing this way.

    --
    My VMS box beat up your Windows box.
    • (Score: 2) by martyb on Wednesday March 08 2017, @12:10PM

      by martyb (76) Subscriber Badge on Wednesday March 08 2017, @12:10PM (#476404) Journal

      I got around this by turning off the *NEW* flag. I left the comment dimming setting on. It's actually been kind of amazing this way.

      Yes, I am aware of this option. The thing is, using Chrome on my smallish Android-based mobile phone, "Find in Page..." and entering this as the search text is a very rapid and accurate way to locate what is new. And works exceedingly well... unless ALL the comments are new, and then it is redundant.

      ISTM that whatever value is saved away after the first time I load a given story could be computed ahead of time, and then used to inform the presentation of the first time I actually view the story. Probably something along the lines of SELECT MAX(cid) FROM comments WHERE sid = '123456'; (or whatever the actual story id is.)

      --
      Wit is intellect, dancing.