Closed
Bug 1472226
Opened 7 years ago
Closed 7 years ago
details pane's content often hidden if multiple treeherder tabs loaded at once
Categories
(Tree Management :: Treeherder: Frontend, defect, P1)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: aryx, Assigned: camd)
References
Details
(Keywords: regression)
When I load several treeherder urls which contain a selected jobs as parameter at once, many of them show the details pane area (identifiable by separator and inspector) but it is empty. The inspector shows it's still set to class="hidden".
Why I load several treeherder URLs at once? Because sql.telemetry.mozilla.org generates a list of jobs whose classification I shall check and then copy the URLs and open them in Firefox. This worked without issues until today.
Likely also from bug 1450022.
Updated•7 years ago
|
Updated•7 years ago
|
Flags: needinfo?(cdawson)
Assignee | ||
Comment 1•7 years ago
|
||
I've been looking at this a bit. I don't have a solid solution yet. I think this may have to do with our React code not getting these values directly and just getting them from Angular. So the timing is off. That's only a SWAG, but I will try a more direct approach to getting the values we need from within React, now that we have the ``JobView`` common ancestor for the main components.
I can reproduce this, but reloading each page once is a work-around for it.
Aryx: What is the priority on this? Can you live with it for a week or so?
Flags: needinfo?(cdawson) → needinfo?(aryx.bugmail)
![]() |
Reporter | |
Comment 2•7 years ago
|
||
Hi Cameron, it can be dealt with it: Rough estimate: (4 people in day shift + 3 people in night shift) * 50 checked jobs * 90% not loading ~ 300 checked jobs/weekday. Quickest workaround seems to hit the spacebar. So costs maybe 15-20 minutes/day.
Flags: needinfo?(aryx.bugmail)
![]() |
Reporter | |
Comment 3•7 years ago
|
||
This is back to normal behavior.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•