Network resource status code in Console lacks contrast

RESOLVED FIXED in Firefox 65

Status

defect
P3
minor
RESOLVED FIXED
9 months ago
5 months ago

People

(Reporter: Harald, Assigned: haque864, Mentored)

Tracking

({good-first-bug})

Trunk
Firefox 65

Firefox Tracking Flags

(firefox65 fixed)

Details

(Whiteboard: [good first verify])

Attachments

(2 attachments)

Reporter

Description

9 months ago
STR:
- Enable Requests in Console and collect some resources during a page load

ER: Green status is dark green background with white text.
AR: Green 200 status is black on dark green.
Reporter

Comment 1

9 months ago
Posted image low-contrast.png
Keywords: good-first-bug
Priority: -- → P3
Assignee

Comment 2

8 months ago
Hi Nicolas,

I would like to work on this. Please assign this to me. Thanks.
Assignee: nobody → haque864
Mentor: nchevobbe
Status: NEW → ASSIGNED
Assignee

Comment 3

8 months ago
Fixes contrast issue of status code in webconsole by creating and importing StatusCode.css file into webconsole/index.html  which contains the rules for styling the Status Code. Also imports the StatusCode.css file to netmonitor.css since status code styles are removed from RequestList.css.

Comment 4

8 months ago
Pushed by nchevobbe@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6447311d0412
fix network resource status code contrastby creating StatusCode.css file containing status code style rules and importing it in webconsole/index.html and netmonitor.css r=nchevobbe

Comment 5

8 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/6447311d0412
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
Whiteboard: [good first verify]

Comment 6

5 months ago

I can see this issue in Nightly 64.0a1 (2018-10-02) (64-bit) in Linux x86_64
I can verify that this is fixed in latest Beta 65.0b10
Build ID         20190110221328
User Agent   Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

[testday-20190111]

You need to log in before you can comment on or make changes to this bug.