Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

17 year old Firefox feature request fixed

bugzilla.mozilla.org

Post reply on HN
Print view View original

181–190 of 281 posts

Re: 17 year old Firefox feature request fixed

#181

Post by Daneel_ »

gdrift wrote: post #45

One 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

Agree with the sentiment in those bug report threads.

The one that grinds my gears is that when you select the URL bar in Chrome it shifts the whole thing to the right, so if you want to edit text you have to reposition the cursor, you can’t just click, pause, then click again.

Re: 17 year old Firefox feature request fixed

#182

Post by Daneel_ »

tus89 wrote: post #123
gdrift wrote: post #45

One 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

A variation on this - Chrome also select the whole address bar, but if you then click a fraction of a second later hoping to position the cursor where you clicked, you find that the https:// appears at the beginning, meaning your cursor is several characters to the left of the position you were hoping for.

Agreed! I find this infuriating. To fix it there’s a flag for “always show full URL”, which I’ve turned on. Fixes it completely.

Re: 17 year old Firefox feature request fixed

#185

Post by namibj »

penteract wrote: post #100
kovac wrote: post #67

Earlier quoted context omitted.

That's interesting. In my case, I hardly edit urls manually in the address bar. Usually I end up on a site either by clicking on links or copying and pasting a whole url from elsewhere. So, when I click on the address bar it's almost always to copy that url. Exception may be if you are front end dev testing different paths on the browser in which case editing in the address bar could be common.

But the automatic single-click selection doesn't fill the X clipboard (meaning it isn't pasted by middle click), so when I want to copy it I have to triple click anyway. Since it looks like it's selected, I frequently forget to do so, which results in pasting something I didn't mean to.

You're referring to selection1, not the clipboard. There is (for me, on Arch) also a selection2, which I haven't investigated further.

Notably Ctrl+C/Ctrl+V operate on the clipboard, while selection and middle-click operate on (at least) selection1.

Re: 17 year old Firefox feature request fixed

#186

Post by jjav »

clankyclanker wrote: post #10

Good 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.

Absolutely. I severely dislike the "bug scrub" attitude that's prevalent in some places that amounts to just closing anything that is not P1 and older than some short time window.

The idea of a bug tracker is to track bugs in the product. If the bug still exists in the code, the bug in the tracker should still be open.

Re: 17 year old Firefox feature request fixed

#187

Post by Agentlien »

CivBase wrote: post #30
dragosmocrii wrote: post #12

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.

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 did try out Rider a little over a year ago. It was really good and I'm impressed with some of its features. But it wasn't enough to make me switch.

Re: 17 year old Firefox feature request fixed

#188

Post by Agentlien »

jjav wrote: post #186
clankyclanker wrote: post #10

Good 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.

Absolutely. I severely dislike the "bug scrub" attitude that's prevalent in some places that amounts to just closing anything that is not P1 and older than some short time window. The idea of a bug tracker is to track bugs in the product. If the bug still exists in the code, the bug in the tracker should still be open.

For open repositories like this I certainly agree. And when I worked at a smaller company with no dedicated QA team we never closed bugs, either.

But in game development with dedicated QA I feel such scrubs are necessary because when they're not done you end up wasting days just confirming that old bugs can no longer be reproduced and flagging them to be closed. Most bugs which linger are symptoms of other bugs which have been addressed.

If they're still there they will almost certainly be found again by QA the moment you close it. In fact, old bugs often even have newer duplicates.

Re: 17 year old Firefox feature request fixed

#189

Post by jhoechtl »

_jal wrote: post #35
clankyclanker wrote: post #10

Good 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…

Did anybody ever find the secret?

Take a look at the root pages html source

Re: 17 year old Firefox feature request fixed

#190

Post by fuzzy2 »

clankyclanker wrote: post #10

Good 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.

The downside is that Mozilla tracks thousands of open tickets, most of which are probably obsolete. But who is going to start now with reviewing stuff from 20 years ago?

As much as it pains me (I’m still tracking multiple bugs I reported) to say this, but all tickets with no activity for some reasonable time period must simply be closed. Things are _already_ out of control.

Post reply on HN