I am never really sure how this feature is helpful, I don't know if I'm being obtuse about the functionality that people give it.
In the JetBrains software I use it all the time but only cause it's clickable.
17 year old Firefox feature request fixed
31–40 of 281 posts
Re: 17 year old Firefox feature request fixed
#32If you're like me, and read the comments first, this change is about giving feedback on the scrollbar for a search. In other words, when you search for something, the scrollbar will give an idea how many results there are, and where on the page rhey are located. On another note, the comment uses IntelliJ as an example. Wow, that was 17 years ago! Happy to see my favorite editor be around for so long.
I’ve been using IntelliJ since version 2. :-) My favorite developer tool of all. Cheers!
Re: 17 year old Firefox feature request fixed
#33Not to get too greedy, but maybe do the 21 year old “Use native context menus on Mac OS” next? https://bugzilla.mozilla.org/show_bug.cgi?id=34572
Looks like it's in progress. Also native "rubberband" scrolling in macOS is in progress as well. Excellent!
Making it also respect dark mode in alerts would be nice.
Re: 17 year old Firefox feature request fixed
#34Earlier quoted context omitted.
Does it? It's not like you're paying GitHub per open issue. I've literally had issues I filed that the maintainer verified as an actual bug be closed due to lack of activity. I can understand that an unpaid maintainer doesn't have the time or motivation to fix it, but closing issues you know are valid seems insane to me.
Is it a human closing it or a bot? If you run an open source project there's a natural tendency to install a bot to auto-close all of the issues which people open because they didn't read the docs, want you to do free consulting for their business, have an irreproducible bug report, etc. and since most projects are short on labor that makes it somewhat inevitable that someone will enable the bot first and never get a…
A bot, but
> someone will enable the bot first and never get around to configuring it to, for example, not close an issue tagged as verified.
I don't understand this part. Aside from the fact that it's trivial to exclude certain tags (it's the same config file, and it's in the first example they give), doing this effectively makes your issue tracker useless as an issue tracker. Why not completely disable the issue tracker instead then?
Re: 17 year old Firefox feature request fixed
#35Good on them for actually tracking this feature request for over a decade and not just closing it after three weeks for “lack of interest.” Looking at you, every random GitHub project ever.
I half-seriously suggested that a project I used to care about set up a cron job to delete requests older than a year automatically.
The rationale was that they only did that sporadically every few years, when some other change mooted the issue. If they ignored feature requests on a schedule, it would better manage external expectations.
See also, The CADT Model (but copy-paste the link in to your browser bar to avoid a bit of unrelated commentary):
Re: 17 year old Firefox feature request fixed
#36Earlier quoted context omitted.
Why is jira.mozilla.com private?
Also, why is there a jira.mozilla.com at all, and why is there a jira.mozilla.COM?
It’s probably private because it is used for internal systems.
It’s probably .com because it’s for Mozilla Corporation as opposed to Mozilla Foundation.
Re: 17 year old Firefox feature request fixed
#37Good on them for actually tracking this feature request for over a decade and not just closing it after three weeks for “lack of interest.” Looking at you, every random GitHub project ever.
I half-seriously suggested that a project I used to care about set up a cron job to delete requests older than a year automatically. The rationale was that they only did that sporadically every few years, when some other change mooted the issue. If they ignored feature requests on a schedule, it would better manage external expectations. See also, The CADT Model (but copy-paste the link in to your browser bar to avoi…
Please remove the link.
Re: 17 year old Firefox feature request fixed
#38Obligatory dogpile, but I'm hoping for the day you can disable Ctrl-Q to prevent accidentally closing the browser with a single keystroke. It's impossible to do on Linux.
Yeah Chrome's "hold to quit" feature is genius. I wish VSCode had it too.
You can hack it in VSCode by turning on the warn-before-terminal-closed feature, and making the terminal always load.
Only drawback (maybe) is that every open project in VSCode warns when trying to close the entire app.
Re: 17 year old Firefox feature request fixed
#39If you're like me, and read the comments first, this change is about giving feedback on the scrollbar for a search. In other words, when you search for something, the scrollbar will give an idea how many results there are, and where on the page rhey are located. On another note, the comment uses IntelliJ as an example. Wow, that was 17 years ago! Happy to see my favorite editor be around for so long.
> 17 years ago "Nearly half my age," said Emacs.
Wait is Emacs lying about its age again?
Re: 17 year old Firefox feature request fixed
#40Good on them for actually tracking this feature request for over a decade and not just closing it after three weeks for “lack of interest.” Looking at you, every random GitHub project ever.
I half-seriously suggested that a project I used to care about set up a cron job to delete requests older than a year automatically. The rationale was that they only did that sporadically every few years, when some other change mooted the issue. If they ignored feature requests on a schedule, it would better manage external expectations. See also, The CADT Model (but copy-paste the link in to your browser bar to avoi…
oh, I love jwz's HN DoS mitigation image.