Show that DPR is not changeable in a better way once you select a device (dark theme)

RESOLVED WONTFIX

Status

()

Firefox
Developer Tools: Responsive Design Mode
P3
minor
RESOLVED WONTFIX
a year ago
a year ago

People

(Reporter: bogdan_maris, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox50 unaffected, firefox51 unaffected, firefox52 affected, firefox53 affected)

Details

(Whiteboard: [rdm-v2])

(Reporter)

Description

a year ago
[Affected versions]:
- Latest Nightly 53.0a1
- Latest Developer Edition 52.0a2

[Affected platforms]:
- Windows 8.1 32-bit
- Windows 10 64-bit
- Ubuntu 16.04 64-bit
- Mac OS X 10.12.1

[Steps to reproduce]:
1. Start Firefox
2. Install a dark theme (https://addons.mozilla.org/en-US/firefox/addon/devedition-theme-enabler/)
2. Visit a random webpage
3. Enter RDM (CTRL+Shift+M / CMD+Alt+M)
4. Click the value of DPR
5. Select a Device from dropdown
6. Click the value of DPR

[Expected result]:
- The disabled dropdown/actions are visible faded out.

[Actual result]:
- No actual visible way of telling if DPR is clickable or not.

[Regression range]:
- This is not a recent regression, it's the same behavior on old Nightly from 2016-11-08 where DPR was enabled for the first time.

[Additional notes]:
- On a non dark theme, DPR is more visible faded out but it and 'No throttling' are always like that until you hover over them (when no devices are selected).
(Reporter)

Updated

a year ago
Has Regression Range: --- → no
Has STR: --- → yes
QA Whiteboard: [qe-rdm]

Updated

a year ago
Has Regression Range: no → irrelevant
Yes, I agree this could be improved.
Priority: -- → P3
Whiteboard: [rdm-v2]
Thinking about this more, I think we actually just want to allow dPR to be changed even when a device is chosen (bug 1319599).

So, I don't think we want to do anything here.  It's probably still true that the colors could be improved in some way, but I don't have any ideas about that for the moment.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.