Closed
Bug 1506424
Opened 6 years ago
Closed 6 years ago
Can't unselect a job by clicking on or near a push's commit messages.
Categories
(Tree Management :: Treeherder: Frontend, defect)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: KWierso, Assigned: camd)
References
Details
Attachments
(1 file)
STR:
1) Load https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cretry%2Crunning%2Cpending%2Crunnable&tier=1%2C2%2C3&group_state=expanded&revision=69f750237e3744322d49179c348a6b409924ed5c&selectedJob=211055260
2) Try to unselect the selected job by clicking either on the push's commit messages or in the whitespace to the right of the commit messages.
Expected:
The job is unselected, just like if you were to click in the whitespace below the commit messages, or any other whitespace on the page.
Actual:
The job remains selected.
I can't remember if this worked in the past before all of the various switches to React.
Updated•6 years ago
|
Flags: needinfo?(cdawson)
Assignee | ||
Comment 1•6 years ago
|
||
You know, the logic to select which clicks clears the selected job is flawed. I have a better idea. :)
Assignee: nobody → cdawson
Status: NEW → ASSIGNED
Flags: needinfo?(cdawson)
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
I had the on-duty sheriff test this and they said it worked in the places she expected it to. :) Wes, if you get a chance to test it locally, that'd be awesome. It worked great for me, fwiw. :)
Reporter | ||
Comment 4•6 years ago
|
||
Seems to work for me.
Comment 5•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/a9c2dedf0a13d4167cc677c117d05c2122d3f90d
Bug 1506424 - Fix logic to unselect job by clicking open areas (#4269)
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 6•6 years ago
|
||
This is now deployed in production.
You need to log in
before you can comment on or make changes to this bug.
Description
•