Closed Bug 1574628 Opened 2 years ago Closed 1 year ago

Improve graph colors and add symbols to better distinguish between tests


(Tree Management :: Perfherder, enhancement, P3)



(Not tracked)



(Reporter: sclements, Assigned: yonashiro.mellina)


(Blocks 1 open bug)



(2 files)

I had made an attempt to improve the graph colors during the most recent react conversion but it fell short as far as being accessible to different types of color blindness, as mentioned here:

In addition to the nocoffee extension Yura mentioned, there are several accessibility features (finding contrast issues and highlighting of the UI) in the devtools panel that will be useful for selecting a new color scheme.

We can also add symbols to the scatterplot once bug 1519995 is merged, details here:

However, we'll also need to add the same symbol to the legend cards, which are separate from the Victory graphs library so that'll require some sort of svg or canvas element creation/drawing mechanism.

Type: defect → enhancement
Depends on: 1519995
Assignee: nobody → yonashiro.mellina

The new feature looks nice but the default shape "Triangle" it's a little misleading for performance sheriffs.

Can we make the default shape a "Circle"/"Dot" please. And also make sure we use "regulated"/symmetric shapes to describe points on the graph.

Triangles then to generate confusion and make us think it's a trend in the graph

Flags: needinfo?(yonashiro.mellina)

Hi Florin,

We have inserted icons to compose Perfherder's graph, in order to help people who are color blind and might have a hard time differentiating the tests.

I understand your concern about the meaning of the symbols. There is another option which is the diamond symbol. I ask you to please take a look at the PR and share your thoughts with me.


Flags: needinfo?(yonashiro.mellina)
Flags: needinfo?(fstrugariu)

I agree with the comments added by Dave and Alex in the pull request. nothing more I can add.

Flags: needinfo?(fstrugariu)
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.