[flagged]
There are various people whose job involves triaging issues filed on that repo, and communicating with the issue authors where necessary e.g. to figure out additional steps required to reproduce the reported problem. The point of that effort is exactly because we value reports of site breakage so highly, and want to ensure that people reporting them have a good experience.
Unfortunately when a bug report (not just this in this repo, but almost anywhere) hits (almost any) social media there's a high chance of the suddenly large audience making comments that aren't at all actionable in fixing the issue. In this case it seems highly unlikely that anyone can add additional information that will allow a faster resolution, whereas there was already one off-topic/unactionable comment at the time the issue was locked.
So if we leave the issue open, it has the downside of disrupting our normal workflows, and taking attention away from fixing either the problem at hand, or any other issues that currently require our attention. To me that significantly outweighs the potential upside of leaving it open to "make people feel welcome".
Of course, like many things in life, it's not a mathematical problem where you can derive a correct answer, but a set of tradeoffs based on experience, and therefore reasonable people may come to different conclusions.
>In this case it seems highly unlikely that anyone can add additional information that will allow a faster resolution
Heaven forbid. Sounds like Mozilla is a wonderful and fun place to work. Lmao.
>of disrupting our normal workflows, and taking attention away from fixing either the problem at hand
People aren't going to die if a few off-topic comments are posted. Holy fuck, what is wrong with you.
>To me that significantly outweighs the potential upside of leaving it open to "make people feel welcome".
That's exactly the problem. Acting like regular users have no worthwhile input is unbelievably out of touch and just plain insufferable. Maybe if you listened more to the user you could build a browser that wasn't such a piece of shit. Lmao.
You clearly look like a very polite person /s
And exactly where are the various QUALITY CONTROL testers that should've caught such a dead-simple problem like "This won't work with Google Search" before it ever happened in the first place?
If I were a web browser coder, making sure my software worked with the major websites of the internet would be the FIRST thing to test. I don't release until I know it works.
This exact same mindset is why I make the expensive stuff where I work, and nobody else.
I'm also not yelling. That you think text is yelling is quite something I'll never understand from anyone. Two capitalized words isn't yelling.
Given this, I can see how this thing can attract low quality comments and have a very low chance of receiving interesting insight.
Now, since we are on HN I'll provide my one low quality comment on this: I guess it's a silly mistake that's not intended, but still feels like another whoops [1].
Also: come on Google, seriously? Don't you have QA for such things?
[1] https://www.zdnet.com/article/former-mozilla-exec-google-has...
The bug is well understood, there's nothing to gain from keeping the issue open and a lot to lose. Getting notifications for "shit posts" is pretty annoying.
_Maybe_ they could have avoided explicitly calling out HN and just said "social media" or whatever. But you're really pulling at straws to get offended here. I don't think their an asshole, I think they're pragmatic.
People will upvote and downvote on this site as they please, and caring about it is a recipe for a bad time.