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

211–220 of 281 posts

Re: 17 year old Firefox feature request fixed

#211

Post by dhekir »

tux3 wrote: post #115
evilpie wrote: post #26

Earlier quoted context omitted.

Good timing! I actually fixed this 21 year old feature request: https://bugzilla.mozilla.org/show_bug.cgi?id=52821 You can set browser.quitShortcut.disabled=true in about config starting with Firefox 87.

Whoa, that is incredible, thank you SO MUCH! I don't think I can explain the extent to which this simple papercut has been vicious and painful to me. So many times, I've started writing some long post in a text field and accidentally lost it due to pressing some wrong keyboard shortcut (oops, you pressed backspace outside a text field! oops, we bound this key to 'reload the page', oops you closed the form by pressing…

Fixing the Ctrl+Q issue is great, but I still think extensions such as Form History Control are essential for all other situations. I'd very much appreciate if Mozilla could vet it for security; I'm always afraid of some developer selling out or being hacked and a future update introducing a backdoor.

Re: 17 year old Firefox feature request fixed

#212

Post by chrisseaton »

mixmastamyk wrote: post #142
chrisseaton wrote: post #98

Earlier quoted context omitted.

Yeah they can't really win - do they try to keep happy a dwindling group who liked Firefox the way it was in the past, or simplify and streamline to innovate more quickly appeal to new users. It's probably impossible to do both. I'm firmly in the anti-customisation camp myself. They obviously aren't ever going to appeal to both of us.

It is possible to do both. The answer is customization, about:config already exists.

> I'm firmly in the anti-customisation camp myself.

> It is possible to do both. The answer is customization

Err well that’s not doing both then is it? That’s having customisation. I don’t want customisation. So that’s not doing both at all that’s just doing it your way and ignoring me.

Re: 17 year old Firefox feature request fixed

#215

Post by scatters »

Daneel_ wrote: post #182
tus89 wrote: post #123

Earlier quoted context omitted.

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.

There may be a flag to "always show full URL"; if it isn't available (in the address bar context menu) you need to go to chrome://flags/, enable the "Context menu show full URLs" option, restart Chrome, and then enable the option.

Re: 17 year old Firefox feature request fixed

#216

Post by sneak »

renewiltord wrote: post #108
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.

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…

jwz has nicknamed this the CADT model, for "cascade of attention-deficit teenagers".

(edit: _jal beat me to it.)

Few things are as infuriating as taking the time to write a great bug report just for it to be ignored or autoclosed.

Re: 17 year old Firefox feature request fixed

#217

Post by olvy0 »

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.

I'm one of the maintainers / developers / support personnel for an internal app that was created circa 1996. We still have open bugs that's 20 years old and haven't yet been fixed.

When I got this role, I instated a culture of never closing old bugs, despite some of my managers wanting me to do that many times, and one of them even going on a rampage once and closing some of them (which I reversed as soon as he left). Some of the bugs are still encountered by new users, unfortunately, but are not fixed yet since they are not critical enough or have enough impact compared to other bugs.

To his credit, that manager also came up with a more-or-less effective formula to rate the bugs according to their importance based on several criteria. Which helps a lot with the upkeep and with planning ahead. And occasionally, one of the very old bugs will be critical enough for a large enough group of users that it will rise up in the ratings to be fixed.

I also set aside time for bug grooming once in a while, closing bugs which were fixed or are no longer relevant. Unfortunately. at this point we are a small team with only 2 experienced devs (the rest are very good but are relatively new graduates and/or without a lot of experience and require supervision) and close to 5000 open bugs and requests, and a steady stream of new feature requests and bug reports. We also have too many internal users for our own good.

It's tough. But the dude abides.

Re: 17 year old Firefox feature request fixed

#218

Post by charcircuit »

zecg wrote: post #214

Now Mozilla, bloody Firefox for Android cannot save the page anymore - not as MHTML, not as PDF. How can such a basic function just disappear?

Because not many people use it. I don't think many people have the desire to save a whole web page. For other unseen you can probably just get away with taking a screenshot, sending the tab / sharing the link, or using an archiving site to save it for later.

Re: 17 year old Firefox feature request fixed

#219

Post by Zecc »

function_seven wrote: post #56
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

I just laughed when I saw your comment, and the bugzilla links are styled as "visted" (i.e. gray instead of black.) I hate that behavior. When I click in the address bar, it's because I want to edit the URL. If I want to go somewhere else, I'll open a new tab, or use a bookmark, or click a link on a page. In the rare case that I want to type a whole new URL, but keep the same tab, I can easily triple-click or [Cmd]+A…

> I just laughed when I saw your comment, and the bugzilla links are styled as "visted" (i.e. gray instead of black.) > > I hate that behavior. When I click in the address bar, it's because I want to edit the URL. If I want to go somewhere else, I'll open a new tab, or use a bookmark, or click a link on a page. In the rare case that I want to type a whole new URL, but keep the same tab, I can easily triple-click or [Cmd]+A before I begin typing.

I'm with you on this. But to me the worst annoyance is how it tends to revert to a previous URL when the new URL fails to load, either because it truly failed to load due to an error or because it timed out while I'm walking through breakpoints.

When I manually entered a URL, the edit should stick even if it doesn't load, dammit.

Re: 17 year old Firefox feature request fixed

#220

Post by unionpivo »

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

Trying to cry in eclipse editor, but its not responding :(
Post reply on HN