New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1600759 - Perfherder's Graph Alt. View for Screen Readers #6001
Bug 1600759 - Perfherder's Graph Alt. View for Screen Readers #6001
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6001 +/- ##
=========================================
+ Coverage 72.06% 72.76% +0.7%
=========================================
Files 456 458 +2
Lines 18905 18988 +83
Branches 1534 1554 +20
=========================================
+ Hits 13623 13817 +194
+ Misses 4957 4842 -115
- Partials 325 329 +4
Continue to review full report at Codecov.
|
Hi @camd and @sarah-clements ,
Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. I'd be curious if you could have Marco give it a test drive on prototype. Or perhaps you already did? :)
Hi @camd, I still didn't talk to him about this PR, but I would love to do it. |
Note that from a markup point of view, this looks good to me. |
Great start! A few comments on the layout/visuals:
|
@bebef1987 @marianrai @alexandru-io please do a manual QA check for this PR, so I know you're ok with the changes done in Graphs view. |
Please add Commit information and a link to treeheder. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a great work and I didn't find functionality issues yet, but in terms of usability the fixes above seem fair to me.
1718e10
to
0ec9304
Compare
0ec9304
to
58b09d6
Compare
@yogmel this looks much better.
Overall this is a good piece of work. Few more fixes and we're good to go. |
e807134
to
2676d24
Compare
In this latest push:
In
|
@alexandru-io Thanks for your input! |
let prevRevision; | ||
let pushUrl; | ||
if (prevFlotDataPointIndex !== -1) { | ||
prevRevision = item.data[prevFlotDataPointIndex].revision; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of this logic from the tooltip can be put into a helper function to be used by both components. That way if it needs to be changed in the future, you only have to change it in that helper function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yogmel, @sarah-clements just be aware that there's an open PR 6066 that is fixing the empty pushlogs from graph tooltip that appears from the second data-point (first retrigger) of a revision. This is because prevRevision
is taking the revision
hash from prevFlotDataPointIndex
, and if the revision is the same, the pushlog link generated is not correct.
Moving this to a helper function might make fixing this bug harder if it doesn't pass dataPointDetails
and testDetails
as params. I don't mind either if you include the fix into this PR. Whatever works best for you. Thanks
This looks good but let's focus on getting this approved and landed. You should do any follow up improvements/functionality and features in a separate pull request, otherwise this will get too big. |
dataIndex, | ||
dataPoint, | ||
highlightAlerts, | ||
highlightedRevisions, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What changed in this file from the last commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2676d24
to
89d0f2f
Compare
I have implemented @sarah-clements's suggestions. About the separation of helpers' functions, I can wait for @alexandru-io merge or implement in the follow-up PR. |
I tested this and I noticed that the 'highlight alerts' button next to the input boxes is controlling the highlighting for the revisions. Those are two separate features (check the implementation in the graphs view). So the toggle for highlight alerts should not control whether the revisions are highlighted. If you want to see a highlighted alert, go to the alerts view and hover over a test - click on the graphs link (the effect on the datapoint is the same). If we don't have the highlight alert functionality implemented in this pr, that button should be hidden until it's implemented. Also, please file new bugs for the additional features to be added. @yogmel you can assign yourself to them, but we should have bugs filed. |
@sarah-clements I have found the piece of code that gets the query params, but I would like to discuss options before making a move. This latest push hides the highlight alerts input in the table view. |
…der improvements, refactor, fix errors
011532e
to
8037617
Compare
@sarah-clements ok, changed to hide only the "Highlight Alerts" button. Input fields are still shown and highlight cells. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - thanks for all your hard work on this :)
Yep, looks good. Even the |
Thank you, everyone :) |
…a#6001) Create a table view in graphs for screen reader users; add tests
Description of issue
Perfherder's Graph View contains graphs and elements which are not screen reader accessible.
Tasks:
Next PR:
Proposed Solution
A button next to "Add test data" was added, to toggle between Graph and Table view.
If there is any highlighted revision, its table row will have a yellow background and an
aria-label
of "highlighted revision".Users can show and hide test via Checkbox in Legend Card:
Testing