Closed Bug 1273929 Opened 8 years ago Closed 5 years ago

[meta] Develop a mechanism for users to more easily diagnose and report graphics-related issues

Categories

(Core :: Graphics, defect, P3)

defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: mconley, Unassigned)

References

Details

(Keywords: feature, meta, Whiteboard: [gfx-noted])

We have some really sophisticated mechanisms in Firefox that allow users to report crashes, and submit various other performance data (Telemetry).

There are classes of graphics issues, however, that we don't make it easy for users to report.

For example, "the black boxing issue", where various parts of content or UI are blacked out. Or smearing when scrolling. Really, there are possibly reams of visual issues that our users are hitting, but have no easy way to report (unless they want to dive into Bugzilla).

We often only hear about these issues in various user forums, so we know they're out there.

What'd be useful is a low-barrier mechanism for users to self-diagnose and/or report graphics corruptions without having to create a Bugzilla account.
Keywords: feature
Whiteboard: [gfx-noted]
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:davidb, maybe it's time to close this bug?
Flags: needinfo?(dbolter)
Maybe Markus is best to decide if leaving this open is useful.
Flags: needinfo?(dbolter) → needinfo?(mstange)
It's still a nice idea, but I don't know of any plans to actually work on this. Let's close it for now, we can reopen if it comes up again.
As WebRender gets rolled out to more GPUs / drivers / OSes, we should probably expect to hit lots of graphics issues of this nature, so having a reporting mechanism for this would be nice... but the WebRender team can worry about it once it gets to that stage. From what I can tell, our current non-Bugzilla reporting channel for these problems is the Firefox subreddit.
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mstange)
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.