Bugs I've filed on browsers
nolanlawson.com
nolanlawson.com
One unfortunate thing is that browsers are probably one of the only remaining major services/applications (that are not directly developer-oriented) which you can report bugs and actually get some tractions, or even get them fixed.
Try to report a bug about MS Word. Or Spotify. Or Google Maps. I've tried all of them and it's safe to say nothing happens no matter how obvious the bug is or how easy it would be fixed. I don't even know if the "feedbacks" I sent ever reached the developers.
For example, recently Google Sheets has a bug that if you input data in the formula bar (instead of directly in the cell) and then press Enter, it somehow enters the edit mode of the next cell, instead of just highlights it like if you edit in the cell. This is driving me crazy and I've filed multiple feedbacks about it, but I have no hope to see it getting fixed any time soon.
It can't be a coincidence that the three apps you mention are all closed source, while both Firefox and Chromium are (at least nominally) open source.
I'd go further than that and say that it's not just not a coincidence, but that I've had the opposite experience in that the vast majority of user-facing programs I've reported bugs against have gotten better responses than anything I've ever submitted to Firefox. The difference is, of course, that every single program on the computer I'm typing this from right now is libre / open source software.
Unfortunately, majority of "large" user-facing programs or services are not open source.
However, most non-source available projects don’t make it possible to publicly track issues at a code level.
On three computers.
In case it was not clear, here is the full STR.
1. Click on a cell. 2. Click on the formula bar. 3. Type something, Press enter (you can even directly press Enter).
Expected: the next cell is highlighted but not in edit mode. So you can use arrow keys to move highlight around.
Observed: the next cell is in edit mode; you cannot move arrow around.
To make it worse, sometimes (but not always), if you press enter AGAIN, it would go to the next (the third one) and STILL in edit mode; you need to press enter AGAIN, which makes the highlight move to the fourth cell, only then it properly exists edit mode.
The bug is also reproducible with Esc (cancel change):
1. Click on a cell; 2. Click on the formula bar; 3. Directly press Esc.
Expected: exit edit mode
Observed: you are still in edit mode. You have to press Esc again.
A gif demo: https://i.imgur.com/KV6rRP6.gif
I registered a new account, and voilà, it suddenly worked!
I compared all the options and couldn't find anything that would cause this until I discovered that my main account's Tools > Accessibility Settings had "Turn on screen reader support" enabled, for which I have no idea why.
I turned it back off, and the issue immediately disappeared.
To be fair, I think enabling this accessibility option shouldn't cause such a bug; but for now, I can finally use it again.
Again, thank you for taking the time to test it!
As for how the site works - make sure you have a microphone and ideally headphones. Click START and you'll hear a metronome. Click ADD TRACK to record a loop. If you're musically inclined you can combine multiple recordings to make a short looping song, by either adding bars to a loop or layering multiple tracks. Hit CTRL or right-click (long press on mobile) a track to modify how it sounds or delete it.
I'll post it to Show HN hopefully soon.
This is an incorrect assumption. Apple engineers prioritize all of their work in Radar, so most of their WebKit bugs will get imported into Radar as a matter of course.
As well as context. I mostly ran into this with webextensions and various cases that a lot of extension developers likely run into that issue less often. It seems, from the outside, that web extensions just generally have a low priority within the team. Which seems, for webextensions, seems to be a very small team anyway as I kept seeing the same three names or so.
Here is an example of one I was involved in (although I did not report it myself): https://bugzilla.mozilla.org/show_bug.cgi?id=1380812
Not as long as your 16 years, but still pretty old. To be fair, there are a few other related issues where work has been done. But all moves at a glacial pace.
And yes, to be clear again, I realize why this doesn't get a lot of priority. It's still a frustrating endeavor.
Mozilla has a huge budget, they just squander it on exec pay and stupid things nobody wants.
tl;dr, whatever the foundation gets, it can't legally spend on the browser.
Firefox is developed by the Mozilla Corporation, a for-profit corporation. This corporation is a wholly owned subsidiary of the 501(c)(3) nonprofit Mozilla Foundation.
In order for an organization to be eligible for 501(c)(3) tax-exempt status, it has to have a “charitable mission”. So it can't just be a “normal” business that simply retains all profits and keeps public financial records. On top of that, if it is determined that the organization is allocating a “significant portion” of its resources to economic activity that does not directly service the nonprofit mission, then it can lose its nonprofit status. Also, lastly, an organization with a 501(c)(3) exemption is literally not allowed to funnel resources into assets which cannot be scrutinized (like a wholly owned for profit subsidiary).
Long story short, literally the only money that Mozilla can use to support Firefox development is the money they get from its commercial ventures, and any profits these commercial ventures would theoretically be for the Mozilla Foundation to use to perform consumer advocacy, which is what they supposedly “really” do, at least as far as the IRS is concerned.
So it is very likely that some of the "stupid things nobody wants" have been initiatives from the foundation.
On top of that, the large majority of revenue of the Mozilla *Corporation* comes from Google as part of a search deal. This makes that income stream very precarious and uncertain.
So, a lot of the remaining things on the list of "stupid things nobody wants" have been the result of the corporation attempting to branch out and find other, more sustainable sources of revenue.
Not to say that all decisions made by the corporation have been to my liking either, but I figured I'd give this context.
I remember an HN thread from probably two years ago about how the Linux version of some software got way more bug reports than the Windows and MacOS versions, despite way fewer users. The bugs were actually mostly cross-platform and non-Linux specific, but Linux users were just more used to actually filing bug reports for the software they used.
[1]?
Yesterday I wrote about fixing M4B audiobook support on Jellyfin iOS/safari without writing any code [0]. When describing the process to my girlfriend I realized it was a kind of skill to know how to navigate a new community and their various communication platforms (GH, Forums, Matrix, socials) and post the right things.
[0] https://blog.rayberger.org/fixing-jellyfin-ios-audiobook-str...
Out of curiosity if you go to https://legacy.python.org/psf/contrib/contrib-form/contribut..., select the top two lines, and do the CTRL L V A C taps does it copy the URL or the text?
Also found a related bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1770723
https://bugzilla.mozilla.org/show_bug.cgi?id=1817233
Who knows maybe one day I'll look into fixing it. Until then I guess I'll just keep using my bash script with raycast that removes newlines and then pastes.
Really enjoy his blog and the posts he did on the PouchDB website.