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

261–270 of 281 posts

Re: 17 year old Firefox feature request fixed

#261

Post by NoodleIncident »

Qwertious wrote: post #151
wongarsu wrote: post #47

Earlier quoted context omitted.

The link is good and insightful, if you copy-paste it into the browser bar. If you click it it redirect to a fairly tasteless image complaining about being linked from HN.

The whole thing is less than a page long and dead simple, I'm just going to copy/paste the entire page verbatim: > The CADT Model >© 2003 Jamie Zawinski >In February 2003, a bunch of the outstanding bugs I'd reported against various GNOME programs over the previous couple of years were all closed as follows: >>Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gn…

Thank you!

> I'm so totally impressed at this Way New Development Paradigm. Let's call it the "Cascade of Attention-Deficit Teenagers" model, or "CADT" for short.

Sounds like the content is just as mature and insightful as the HN ddos redirect image. I see why objecting to being linked an image of a hairy ball in a 2011 image macro was wrong of me.

Re: 17 year old Firefox feature request fixed

#263

Post by intrasight »

herodoturtle wrote: post #254
intrasight wrote: post #248

Earlier quoted context omitted.

Emacs of course ;) Gosh, "old timer" :(

Apologies for my poor choice of wording! Here in South Africa we typically use "old-timer" to refer to someone who is very experienced. My comment was expressed with the utmost respect I assure you :)

I didn't take it as a derogatory label. My emoji was just my own self reflection on the years gone by.

Re: 17 year old Firefox feature request fixed

#264

Post by IshKebab »

ryandrake wrote: post #102
IshKebab wrote: post #11

Earlier quoted context omitted.

Yeah Chrome's "hold to quit" feature is genius. I wish VSCode had it too.

Uggh. I pretty much never use Chrome on my Mac, but when I borrow someone else's computer and want to quit Chrome I always get bit by this one! No other application have I seen that makes you hold down ⌘Q to quit, except for Chrome. This is not conventional on Mac apps! It's probably configurable but why make it the default?

Because nobody would know it even existed if it wasn't the default and it's a great feature!

Re: 17 year old Firefox feature request fixed

#265

Post by samus »

mschaef wrote: post #242
jjav wrote: post #186

Earlier quoted context omitted.

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.

The counterargument is that a bug is enough a function of its context that the older they get, the less likely they are to still be relevant or accurately documented. Having a bug on the list isn't enough - it needs to be periodically reviewed, kept up to date, prioritized, etc. Sometimes the overhead of that maintenance work isn't worth it, particularly for a bug that's been explicitly categorized as 'low priority'…

This assumes that the bug creator can be bothered to review the bug and type every n weeks "still happens", with n unknown and variable in general. This makes sense for an organization with clear processes where the value of n is well-known to all stakeholders, but comes off as unwelcoming and offputting for users who want to contribute in their free time to improve their favorite applications.

Re: 17 year old Firefox feature request fixed

#267

Post by firexcy »

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?

I also find this painful and have switched to iceraven, a fork of Firefox Android that supports arbitrary addons, and use SingleFile to save webpages as html files.

Re: 17 year old Firefox feature request fixed

#268

Post by firexcy »

Glad they finally add this. Used to be a painful lack compared to chromium-based browsers. During the long wait I've found this amazing addon called HighlightAll [1], which allows you to search multiple keywords and highlight them with different colors; the position will also be labelled on the scroll bar. Super helpful for researching/consuming long articles.

[1]: http://jgoudey.free.fr/highlightall/

Re: 17 year old Firefox feature request fixed

#269

Post by smichel17 »

mschaef wrote: post #242
jjav wrote: post #186

Earlier quoted context omitted.

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.

The counterargument is that a bug is enough a function of its context that the older they get, the less likely they are to still be relevant or accurately documented. Having a bug on the list isn't enough - it needs to be periodically reviewed, kept up to date, prioritized, etc. Sometimes the overhead of that maintenance work isn't worth it, particularly for a bug that's been explicitly categorized as 'low priority'…

I think it's actually a problem with issue trackers, which have only this binary open/closed status, where the only way to express "outdated" is with a label or something.

As a project maintainer, I don't want to close unfixed issues because they become much harder to find (hidden by default), which results in duplicate reports if it turns out the issue is not fixed. Also it can be rude, if it was a high effort bug report.

At the same time, I don't want to leave open years-old issues about a part of the program which has been heavily modified, because they are likely outdated, and low priority to begin with.

The best compromise for the moment seems to be leaving them open, tagging them as outdated or someday/maybe, and filtering out those tags. This is far from ideal, because the filter isn't sticky, so you either have to bookmark it or continually re-apply it.

But it would be really nice if bug trackers created three visual bins to dump things into, where the middle bin is this nebulous "stuff" that's not quite groomed well enough to be actionable but also not finished enough to be closed. (Note: also, "closed" should be subdivided into "implemented" and "rejected" with different visual statuses, like Merge Requests often are distinctly coloured by merged vs closed -- but this is not a separate bin).

Re: 17 year old Firefox feature request fixed

#270

Post by roryokane »

iFreilicht wrote: post #210
tux3 wrote: post #115

Earlier quoted context omitted.

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…

Oh god yes, backspace outside the text box is the worst. Some websites mitigate this themselves, but it would really be nice if the browser could take care of this.

Firefox already lets you disable that using the browser.backspace_action setting in about:config: https://support.mozilla.org/en-US/questions/924490
Post reply on HN