Hacker News new | comments | show | ask | jobs | submit login

marking a comment up or down should use ajax- especially so browser history is preserved (pressing the back-button to get to the front page). I assume comments can be marked into the negative range for those hopefully rare occasions where it's needed? [please don't test it on me!]. Other than that I love the minimalism.

What about a separate feature requests page for those that already have been accepted and implemented like this one? And maybe another for formal rejections.

I think it can get confusing reading suggestions for features that have been implemented since the request was made for less obvious features than ajax voting. And they're not particularly relevant anymore. Of course I wouldn't simply delete them so a separate page would be a good compromise.

>marking a comment up or down should use ajax

Without ajax I'm sometimes discouraged from voting at all, because it's difficult to find my location after a refresh, especially on long pages.

It doesn't even really have to be AJAX. You could solve the problem just by setting up an #anchor so that when the screen reloads after voting, it just the user back to where they left off.

I would like to second, third, or fourth this. Having the page jump around when I vote on something really makes me not want to use the site.

Normally I hate "me too" posts, but I feel this feature is important enough that I wouldn't want you to think other people didn't agree. Thanks.

if you have firefox and greasemonkey, this script might be what you're looking for: http://userscripts.org/scripts/show/8951

that doesn't solve the problem that I (and I assume others) habitually press the back button when I'm done perusing comments in order to get to the main page. At this point when I press the back button it goes to a slightly older version of the comments page- and various other oddities.

I run into this problem all the time--not good for diminishing by reload-addiction! It would be nice if pages included some js to rewrite history[1] via dom, so that we could always see the freshest versions of pages.

[1] It pains me to advocate breaking the "show me exactly what I was just seeing" semantics of the back button, but I think in this case the user clearly conceives the back button as "show me the abstract resource I was just seeing."

I'm just going to point out that this really makes me only vote on topics I really care about. It doesn't really bother me.

I agree with this suggestion, but for another reason. There have been a few times when I'm writing a reply and I stop to think for a moment. Occasionally, during this pause, I will glance up and notice that I haven't voted the article up yet. Unfortunately, when I do vote the article up, everything I have written up to that point gets cleared. I have tried pressing the back button, but it tends to take me back to where I was before I started writing my comment.

I understand that this is an error on my part, but that doesn't alter how frustrating it can be.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact