12 years ago
12 years ago


(Reporter: philor, Assigned: philor)



Firefox 3 beta1
Dependency tree / graph
Bug Flags:
blocking-firefox3 +

Firefox Tracking Flags

(Not tracked)



(1 obsolete attachment)



12 years ago
Posted patch Disable it (obsolete) — Splinter Review
While it would certainly be nicer to have bug 389128 and bug 389131 fixed, apparently raccettura only has one working wrist, and there's no sign of anyone picking them up for him, so we're set to ship a beta so that people can test whether there are broken web sites, with a menuitem that we know doesn't work to Report Broken Web Site...
Flags: blocking-firefox3?
Attachment #285629 - Flags: review?(mconnor)
Do we have stats on how many people are submitting broken sites by this method. Might be useful for deciding whether to push more resources on reporter rather than just removing it.

Comment 2

12 years ago
To the (totally unknown to me) extent that is correct, of the 742089 reports, we got a couple hundred from each 3.0 alpha until it broke with a7. 2.0 alphas got around 400 each, while 2.0 betas got a couple thousand each.
I had found that and its not the stats I was looking for at all. What I meant was how often are people using this tool (regardless of app/version)

Comment 4

12 years ago
Well, it also says 1188 in 24 hours, 7414 in 7 days, so I guess those would be the "give up on it completely" numbers.
Hmm I must be blind. So 1000 reports a day does not sound like "yeah lets ditch this without thinking much about it".
to chime in...

it's mostly done... just needs someone to handle changes necessary for r=.  I can advise a volunteer as needed... just not up for too much @ the sec (changes, testing, etc).
Plussing so we don't lose the red button, but I think Robert's got this now...
Flags: blocking-firefox3? → blocking-firefox3+
Whiteboard: [has patch][nuclear option]

Comment 8

12 years ago
Bug 389131 is fixed so is this still needed?

Comment 9

12 years ago
Yup. It was filed on the state where you couldn't successfully submit a report with Reporter, and if you build right this second, you can't successfully submit a report with Reporter. I think we can manage to remember not to land this patch while we wait for bug 401816 to successfully land-and-stick, rather than ping-pong this bug if bug 401816 has troubles or delays or bug 389128 winds up needing another round. Not to worry, I'll gleefully wontfix it as soon as it's clearly and certainly not needed.
Comment on attachment 285629 [details] [diff] [review]
Disable it

reporter is almost no longer useless, waiting on bug 401816
Attachment #285629 - Attachment is obsolete: true
Attachment #285629 - Flags: review?(mconnor)
Last Resolved: 12 years ago
Resolution: --- → INVALID
Whiteboard: [has patch][nuclear option]

Comment 11

12 years ago
Or, I guess we could go with the premature potential ping-pong :)
verified - the reporter UI was working fine during my tests in Bug 401816
You need to log in before you can comment on or make changes to this bug.