Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are users in the comments here reporting the issue affects them.

Would some noble purpose be served by closing the existing issue in the hope that they'll complain via more official channels?



Hopefully those people will report the issue in the bug report and try to help the devs reproduce the issue. Especially since it is linked.


I don't think one more user report is going to be the difference that pushes them over the finish line after two decades. Let's not pretend the developers have been taking this bug seriously.


They still have it marked as unreproducible. What do you expect them to do if they can't reproduce?

So yeah, I do think more user reports can help. At worse, it will make them take it more seriously if there are more reports.

You also are falling to observation bias. You can see linked in the issue as well as by searching that there are similar issues that were resolved and marked solved. So I don't think they were just doing nothing as everyone seems to be assuming.


Have the been any potential fixes made since those reports?


Given there are people in the comments here indicating the issue still exists, there haven’t been any actual fixes made.




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

Search: