Closed Bug 1149687 Opened 10 years ago Closed 10 years ago

Strange layout (with flexbox) in the list of links in the job results pane on profiled Talos runs

Categories

(Tree Management :: Treeherder, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mstange, Assigned: wlach)

References

Details

Attachments

(2 files, 2 obsolete files)

Attached image screenshot
On this push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=212ea0836d66 If you select one of the Linux x64 "o" Talos jobs, the stuff in the bottom pane looks strange. The list items of the "Open ... in cleopatra" links should be below each other, instead of besides each other.
The container for all those "open...in cleopatra" links is a row-oriented flex container right now. For its children to stack vertically, you need to either give it: - flex-direction: column ...or probably-better... - display:block (since it's just a bulleted list, and you're not actually making use of its flexiness at all. Flex containers have complicated perf properties, and if you don't actually need to make the "open in cleopatra" align or flex in any particular flexbox-defined way, then a block is probably better.)
The "Datazilla/Graphserver" bulleted <ul>-list doesn't seem to have "display:flex" -- it's just a block (as I'd recommend, per end of comment 1). So, I suspect the other <ul> is getting *accidentally* styled as a flex container. It's getting that style from this complicated CSS selector: #bottom-center-bottom > *, #bottom-center-bottom > * > *, #bottom-center-bottom > * > * > * I'll bet that style isn't intended to target this <ul> element (though it does). If you put a wrapper <span> or <div> around it (as we have around the "Datazilla/Graphserver" list), then I think the CSS selector would target that wrapper instead of targeting the <ul> itself. Maybe that's what was intended here?
Attached image spanApproachProposed (obsolete) —
With the span/div addition, we'd have two columns for the data (attached) if you guys prefer that. Otherwise yes, perhaps we could override the css and make the ul display:block and have everything in one tall single column. I guess it depends on how narrow Talos users expect to work with the browser vs. having data off screen perhaps more frequently.
The <ul> should already be display:block -- the only reason it wasn't is because it was at an unexpected nesting-level, I think, and so the selector in comment 2 was hitting it when it wasn't intended to. If you want everything to render in a single column, you'd want to just put both <ul> elements in the same <span>, instead of two different spans (& instead of having the second <ul> be a sibling of the first <span>, as is the case right now).
Attached image proposed (obsolete) —
Right, here's that look if you guys would like single column instead.
Attachment #8586356 - Attachment is obsolete: true
mstange said it used to look like that (single column for the bulleted lists), BTW - he linked to: https://wiki.mozilla.org/images/0/04/Treeherder_talos_profiling_cleopatra_links.png (I'm not sure if the switch to the current UI -- moving in the direction of two columns -- was intentional or not.)
I think single column makes more sense, agreed. I'll put up a PR momentarily so we have something workable. We can always tune/tweak later. Thanks for the guidance Daniel :)
Assignee: nobody → tojonmz
Status: NEW → ASSIGNED
Turns out wlach and I were working on this in parallel, so re-assigning :)
Assignee: tojonmz → wlachance
Priority: -- → P2
Depends on: 1094466
Attached file Temporary fix
Temporary fix until root cause (bug 1094466) is fixed. This is probably a small improvement in any case though, as it makes a bit more sense IMO in how we separate the different elements.
Attachment #8586365 - Attachment is obsolete: true
Attachment #8586395 - Flags: review?(tojonmz)
Comment on attachment 8586395 [details] [review] Temporary fix Looks good, and I also tested the branch locally and it seems fine.
Attachment #8586395 - Flags: review?(tojonmz) → review+
Cool, going to resolve this bug for now.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: