If 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.
17 year old Firefox feature request fixed
191–200 of 281 posts
Re: 17 year old Firefox feature request fixed
#192Good 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.
Also Gnome. Always cracked me up. Like I'd make this issue with like all the details reported and everything. ESR would have wept. And then "Does this issue still occur in Gnome 3?" and closed a week later all while I'm on vacation. Homie, this sat here for like 5 years, surely you can be a little patient. Anyway, that taught me not to report something that's not a game-ender. Which is probably what they want too, so…
Re: 17 year old Firefox feature request fixed
#193One of the most voted for issues is closed WONTFIX: single click selects all in address bar and search box. I use Firefox exclusively and this is the single most annoying change they made for no apparent reason. So annoying. https://bugzilla.mozilla.org/show_bug.cgi?id=1621570 https://bugzilla.mozilla.org/buglist.cgi?votes=133
Re: 17 year old Firefox feature request fixed
#194Re: 17 year old Firefox feature request fixed
#195Not 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!
Re: 17 year old Firefox feature request fixed
#196Earlier quoted context omitted.
Most of the times when I interact with the address bar it's either to go to a different site, google something or copy the url - in all of those use cases I interact with the entire address to either replace it or select it. I would wager almost anything that this is the case for the vast majority of regular users because most of the ones I've interviewed (N = 31) for a uni UX study didn't even know how to read URLs…
It's sad but true. Googling is probably Firefox's only feature left. After they trashed the dev ecosystem, removed file access, prevented 127. access and prevented ssl bypass for 10. and 192.168. broke markdown rendering, disabled CD access, made development painful, fsckd ftp, banned useful stuff on file:// removed anything useful from about: made developing inside Firefox a nonstarter, borked Web app, and generally…
Re: 17 year old Firefox feature request fixed
#197Earlier quoted context omitted.
To think I was still using Eclipse a scant 7 years ago...
I was forced to use Eclipse for a while ~2010, never liked it. It's funny to look at how many editors one comes across over the years. My first one was Borland C++ as a kid. Then came a mix of Visual C++ and Bloodshed Dev C++ during high school. During university I tried a bunch of things but mainly nano, gedit, Visual Studio, and Eclipse. In my early career (2013) I finally got into Vim and haven't looked back since…
I find it a great way to combine the strengths of Vim with the strengths of a full IDE.
Re: 17 year old Firefox feature request fixed
#198Earlier quoted context omitted.
Is that talking about the right-click menus, or something different? The right-click menus look and act native to me.
This is what the right-click menu looks like in Firefox on macOS [1]. Compared to the right-click menu from Safari on the same machine [2], you can see several differences. The most notable one is that the Firefox menu is not theme-aware, rendering a light-themed context menu even though the OS is in dark mode. Next, the padding around the menu is incorrect compared to a native menu. It also looks like the font is ma…
Basically, they are not at all the same.
Re: 17 year old Firefox feature request fixed
#199If 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.
To think I was still using Eclipse a scant 7 years ago...
What do you think is the biggest difference between the two?
Re: 17 year old Firefox feature request fixed
#200If 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.
To think I was still using Eclipse a scant 7 years ago...
But, I've since switched to intellij for Java (and later, lightweight editors like Sublime Text for JS, until a while later JS finally got modules and editors added more support for JS), and nowadays I'm using it for everything; I'm currently managing a 200KLOC application (it's too much but my employer isn't hiring, sigh) in at least four languages (JS, PHP, TS and Go, it's an older application and a rebuild I'm working on), and intellij has no qualms with it whatsoever.
I even set it to PHP 5.2 mode so it warns me when I try to use `[]` to initialize an array.