So many of the top comments on HN posts are complaints about website functionality rather than the content of the site. I'm all for not breaking standards but sometimes it gets old when the top content is a negative content about the use of javascript or ux. Bracing for downvotes

You're right, and it's a long running problem. See what dang says here: https://news.ycombinator.com/item?id=9238739

> A reader emailed to complain about how this and other HN discussions often become derailed by off-topic carping about blog design. I agree completely. Could there be a more classic form of bikeshedding? It would seem parodic if it weren't sadly real. This has become more of a thing on HN lately. It needs to become less of a thing.

> I don't mean to pick on you personally, or just on this one comment. (Your second sentence alone, by the way, would have been a helpful contribution.) The problem is the tedious stampedes such comments spawn.

Maybe, after enough shaming, the people who break browsers will stop doing so

I often check out comments and use that to decide whether to go to the actual link.

A high ranked complaint about website functionality can help me make that decision, and I am happy to upvote complaints that would sway me.

Agreed, I’m going to start flagging such comments because they really harm the quality of discussion. If I lose my flagging privileges as a result, so be it.

As you scroll through the site it seems to re-set the current page for each section, which was totally unexpected behavior to me.

Likely a history.pushState vs history.replaceState bug (they want the latter)

On all browsers (with history api’s) most likely, looks like they are multiple entries without replacing one.