Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time
-
I just got a slew of "request for more information" emails from Bugzilla for bugs I had submitted for Firefox.
In 2012.
Most of them were "oh hi is this still happen in current?"Keep in mind these were filed against FF17.
To which I reply:
I don't know. I haven't upgraded past FF22 due to all the anti-features and adware.And then my favorite:
Of note in the bug report:
FF17, jQuery 1.8.3, jQuery Mobile 1.2.0 final. Same code was working fine in FF16, still works in IE, Chrome, etc.
Could you attach a minimal testcase, please.
Uh, sure, 4 years after the fact I'll get right on installing FF17, an old jQuery and an effectively deprecated mobile framework. Seriously?
-
@Lorne-Kates said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
Could you attach a minimal testcase, please.
Playing Devil's Advocate here, that request originally came 2 days after the bug report, but I'm betting you didn't get an email for that reply, just the one 4 years later.
-
@Lorne-Kates said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
I just got a slew of "request for more information" emails from Bugzilla for bugs I had submitted for Firefox.
In 2012.
Most of them were "oh hi is this still happen in current?"Keep in mind these were filed against FF17.
To which I reply:
I don't know. I haven't upgraded past FF22 due to all the anti-features and adware.And then my favorite:
Of note in the bug report:
FF17, jQuery 1.8.3, jQuery Mobile 1.2.0 final. Same code was working fine in FF16, still works in IE, Chrome, etc.
Could you attach a minimal testcase, please. Uh, sure, 4 years after the fact I'll get right on installing FF17, an old jQuery and an effectively deprecated mobile framework. Seriously?You were asked 4 years ago to:
Could you attach a minimal testcase, please.
Had you done your civil duty to attach a test case all those years ago, FF would not be in as shitty as it is now! IT IS ALL YOUR FAULT!!!!
-
@ChaosTheEternal said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
Playing Devil's Advocate here, that request originally came 2 days after the bug report, but I'm betting you didn't get an email for that reply, just the one 4 years later.
Nope, never got the email 4years-2days ago.
Not that it would have helped. I've given them test cases before and they either reply with:
- WOMM
- OMFG THAT IS AN ASPX SITE HISSSSSSSSSSSS
Literally all they had to do was create HelloWorld.html with those two libraries I mentioned, and the error would show up. Fuck their lazy "do my job for me" asses.
-
@dse said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
Had you done your civil duty to attach a test case all those years ago, FF would not be in as shitty as it is now! IT IS ALL YOUR FAULT!!!!
Also, jQueryMobile would be the #1 mobile framework, and not Bootstrap.
I have failed this
cityinternet.
-
@dse said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
Had you done your civil duty to attach a test case all those years ago, FF would not be in as shitty as it is now! IT IS ALL YOUR FAULT!!!!
Well, I see you are an optimist.
-
@ChaosTheEternal
He got an e-mail, but he couldn't open it because he was using Thunderbird 0.22, and there was a bug in that version that automatically deleted e-mails from Mozilla's bug tracker. Sadly, @Lorne-Kates never updates past a version that includes the sacred number 22.
-
@izzion it's generally a bad idea to draw Our Lady's attention by using version 23
-
@Lorne-Kates said in Mozilla's Blinding Fast and Super Useful Bug Report Turnaround time:
Nope, never got the email 4years-2days ago.
But I usually get emails for my bugzilla issues years later, with something like:
Since no one in this universe is still using version 18.2 I am going to smash this 
out of existence, as if it never existed
-
add ghooks 路 Pull Request #11 路 boomzillawtf/tdwtf
This adds git hooks to force users to npm update when they pull, npm run lint when they commit, and npm test when they push. If these tasks fail, the commit or push fails.
814680 - Permission denied to access property "role"
