Good. Can we have webmidi next?
Don't we already? I thought I used that before.
Not on FF in the standard config. Chrome yes. Webaudio does work, maybe that confused you?
17 year old Firefox feature request fixed
221–230 of 281 posts
Re: 17 year old Firefox feature request fixed
#222Great, now maybe they can fix the size of adding bookmarks window. https://bugzilla.mozilla.org/show_bug.cgi?id=219972 My favorite bug, 18 years old, closed without replacement.
The bug you linked is about the properties window of an existing bookmark, which is resizable.
Re: 17 year old Firefox feature request fixed
#223Good 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.
Just do what they do where I work, move to a new tracking product, if you really care then you have to go and open bugs in the new (more annoying to use) system :)
We're on our 3rd or 4th now.
Re: 17 year old Firefox feature request fixed
#224Earlier quoted context omitted.
I really miss Camino.
Now that’s a name I’ve not heard in a long time.
Yup, a long, long time ago, in a galaxy far, far away.
For its time it was a great little browser. I was going to do some bug fixing on it. But then I saw that it required Corba ORB to build. So I let out a long, low moan and, shivering uncontrollably, filed that dream under never going to happen.
Re: 17 year old Firefox feature request fixed
#225Now 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.
"Because not many people use it" was the excuse Google gave for killing RSS.
Re: 17 year old Firefox feature request fixed
#226I hope they also finally allow black on yellow highlighting again (like pretty much every other browser), which hasn’t been possible since Firefox 3.5 in 2009. https://bugzilla.mozilla.org/show_bug.cgi?id=505089 http://forums.mozillazine.org/viewtopic.php?p=7018785
btw black on yellow is used for the tag. it makes sense to not use the same colors for firefox chrome
Re: 17 year old Firefox feature request fixed
#227One 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
Agreed, maddening. I kept my Firefox installation pinned to 74 for as long as I could because of this, but I had to give in and update to 85 a couple of weeks ago for something. I scan the release notes for each release in hope, but no.
I don't really care about consistency with other browsers - I don't use other browsers very much. I care about consistency with everything else on my desktop.
(It's not just about the option - I didn't even use the browser.urlbar.clickSelectsAll option myself. The clickSelectsAll=false behaviour - the one that was removed - had been the default on Linux.)
Re: 17 year old Firefox feature request fixed
#228Earlier quoted context omitted.
Wontfixzilla with comments disabled is a clear statement. Is a wontfix with lots of comments more expensive, than a wontfix with comments blocked? Shame you cant "give the devs opinion" on bugzilla.
I'm not totally following what you're saying, but I can answer this: > Is a wontfix with lots of comments more expensive, than a wontfix with comments blocked? Yes, it is more expensive. When 100 developers are CC'd on a bug that is generating regular "but did you consider this argument?" comments, it's a lot of overhead. You could argue that everyone CC'd should remove themselves from the CC list when this happens,…
> These bugs are not fun for anybody, dev or unhappy user alike.
Then fix them.
Re: 17 year old Firefox feature request fixed
#229Of course, there used to be an add-on that added this functionality, but was subsequently killed by the 57 update.
Re: 17 year old Firefox feature request fixed
#230Earlier quoted context omitted.
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…
There's an official Vim plugin by Jetbrains for all Jetbrains IDEs (including Rider). I find it a great way to combine the strengths of Vim with the strengths of a full IDE.
Here's another vouch for IdeaVIM. It's got 99% of the VIM that I use, and is actively developed.