"GPU Accelerated Windows 0/1" needs to be simplified to prevent user confusion

RESOLVED FIXED in mozilla11

Status

()

Core
Graphics
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: Dave Garrett, Assigned: Atul Aggarwal)

Tracking

(Blocks: 1 bug)

Trunk
mozilla11
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mentor=joe@drew.ca])

Attachments

(1 attachment)

1.11 KB, patch
Joe Drew (not getting mail)
: review+
Details | Diff | Splinter Review
(Reporter)

Description

7 years ago
A user asked in another bug what "GPU Accelerated Windows 0/1" means? It means nothing is accelerated: zero out of a possible one windows. That's nice and cryptic for the about:support page.

Please make this case simpler. When there is no acceleration enabled, simply say "No GPU Acceleration" or just "none" in place of "0/1" or any "0/n".
(Reporter)

Updated

7 years ago
Blocks: 594464
(Reporter)

Comment 1

7 years ago
Even just a plain "0" would be preferable, actually.
Have users been confused by (for example) 2/2 Direct3D 9?
(Reporter)

Comment 3

7 years ago
I don't know. I would guess it's possible. If you want to reformat entirely, I'd suggest something along the lines of:

GPU Accelerated Windows:
    x accelerated windows (y total windows open) using _____ for acceleration
(Reporter)

Comment 4

7 years ago
I'm putting "[strings]" on the whiteboard, but if you're stringphobic right now just comment 1 would suffice as a bare minimum for my initial case.

If we could get the full clarification of comment 3 + comment 0 ("none" or "No GPU Acceleration" when applicable) that would be the best solution.
Whiteboard: [strings]
It's not particularly important that users understand everything on about:support, given its purpose. I don't think we should spend time trying to fix this now.
Whiteboard: [strings]
(Reporter)

Comment 6

7 years ago
Then I'll take the lazy fix if you don't think it's worth bothering with the more explanatory one.

http://hg.mozilla.org/mozilla-central/file/76b7f615bab9/toolkit/content/aboutSupport.js#l219

219   let msg = acceleratedWindows + "/" + totalWindows;
220   if (acceleratedWindows)
221     msg += " " + mgrType;

Just move the "/n" part down a bit to be:

219   let msg = acceleratedWindows;
220   if (acceleratedWindows)
221     msg += "/" + totalWindows + " " + mgrType;

I'd submit an actual patch, but I don't have an hg checkout or build environment for Firefox.
Sure, I'd be fine with that.
Keywords: ue, ux-feedback, ux-jargon
I believe comment 6 should be enough for someone to implement this, but should that not be the case, please ask me questions!
Whiteboard: [mentor=joe@drew.ca]
(Assignee)

Comment 9

6 years ago
Created attachment 577154 [details] [diff] [review]
Patch v1

What's current consensuses regarding this bug? Complete rewrite or just simply displaying "0". In case of later, attaching the patch.
Assignee: nobody → atulagrwl
Attachment #577154 - Flags: review?(joe)
Comment on attachment 577154 [details] [diff] [review]
Patch v1

Review of attachment 577154 [details] [diff] [review]:
-----------------------------------------------------------------

I'm fine with this. I don't have any real feeling on whether it fulfills the intent of this bug, though!
Attachment #577154 - Flags: review?(joe) → review+
(Assignee)

Comment 11

6 years ago
I definitely think it will prevent confusion among users. I also got confused first time when I looked at 0/1 (It looks like either 0 or 1 or something in those lines). It can be '0 of 1' also.
Keywords: checkin-needed
http://hg.mozilla.org/integration/mozilla-inbound/rev/a99b6b77bcc4
Keywords: checkin-needed
Target Milestone: --- → mozilla11
https://hg.mozilla.org/mozilla-central/rev/a99b6b77bcc4
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.