Jonathan French (:jfrench) Assignee
	Description • 9 years ago

We presently have these full text-buttons in logviewer-actionbar:

[icon] open raw log
[icon] open analyser
[icon] show successful steps

In their current layout they consume an extra "line" of potential content under the steps container. We'd like to preserve their text identification rather than just icons, based on earlier user feedback.

We also had recent feedback from jgriffin expressing an interest that they take up less space. I'm curious if folks might be receptive for rawlog/analyser to any of:

1) integrating them into the RH side of the colored header "Result" bar (ie. to the right of "testfailed", "busted")
2) integrating them into some sort of dropdown 'Action menu' similar to Treeherder's resultsets bar, perhaps in the same location above (though might be annoying for quick reftest access)
3) integrating them into some sort of global logviewer navbar (would still consume a line)

and:
4a) doing something clever, obvious and inuitive with "show successful steps" which might allow us to not use its adjacent text

It's not an easy problem to solve, but soliciting a couple of logviewer and reftest analyser users for their opinions.

nb. I have a change for another bug and plan to reduce font size slightly for the entire upper container.

	Jonathan French (:jfrench) Assignee
	Comment 1 • 9 years ago

Anyone on the recipient list also feel free to chime in :)

	Kartikaya Gupta (email:kats@mozilla.staktrace.com)
	Comment 2 • 9 years ago

FWIW this is what I see on the logviewer page. It seems to me that you can just move the actionbar over to the left column (under "Revision") and that would save you a line of space. Not sure what jgriffin was referring to when he asked that they take up less space - did he say he wanted more space for the log pane at the bottom? Or just that the buttons were too big and he wanted them taking up fewer pixels on screen? I don't really have an opinion on this either way, I always use the plaintext full log view rather than the logviewer (even when handed a link to the logviewer the first thing I do is go to the plaintext version).

	Ryan VanderMeulen [:RyanVM]
	Comment 3 • 9 years ago

I wouldn't mind seeing a mockup of kats' suggestion with the buttons moved over to the left side.

	Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)
	Comment 4 • 9 years ago

It actually depends on how many failures are in the log (and how long the failure lines are). Currently, if there's only one or two failure lines (or the failures are short and succinct), the actionbar fits underneath the current right side.

	Jonathan French (:jfrench) Assignee
	Comment 5 • 9 years ago

(side note) I'm also about to fully fill the left side (header/metadata) container with bug 1092209 by including the Job details tinderbox printlines, so I anticipate it the header will always overflow and use its full container height. Although we could still consider concept 1 or 2 posed in the Description. I'll try to mock something up when I get a chance.

	David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)
	Comment 6 • 9 years ago

My only comment would be that moving them to secondary UI, especially the reftest analyzer button, isn't great, since when I see a reftest failure link from bugzilla, I get to the logviewer page, and the only thing I do with it is use it to get to the reftest analyzer.  So I'd rather that link be easily visible.  That concern is specific to reftests, though.

	Jonathan French (:jfrench) Assignee
	Comment 7 • 9 years ago

Thanks everyone. Here's roughly what I'd like to propose then for the logviewer which is proposal 3) in comment 0. It also addresses bug 1183880 and while doesn't economize a line like my original proposals 1) or 2) it keeps the buttons as primary UI and allows for additional buttons later on without running out of space, as we would with the current layout.

It will also space for different controls in the navbar for later on. eg. a potential collapse/expand button for run-data container, etc.

I'm also proposing a navigation menu back to Treeherder via its logo button on the left side. Same as Treeherder and Perfherder. Even though we can do that indirectly via the 'Revision' link, it would be a global nav back to Treeherder's mozilla-inbound.

Let me know what you think.

	Jonathan French (:jfrench) Assignee
	Comment 8 • 9 years ago

I've received positive feedback on the mock in channel from about half a dozen people, and no negative feedback, so I intend to start work on it next week.

	Jonathan Griffin (:jgriffin)
	Comment 9 • 9 years ago

Nice, I like this too.

	Jonathan French (:jfrench) Assignee
	Comment 10 • 9 years ago

Please see above PR for review at your leisure :)

	William Lachance (:wlach)
	Comment 11 • 9 years ago

Comment on attachment 8640546 [details] [review]
PR 817

This looks great, nothing jumps out at me that I'd change.

	Treeherder GitHub Bugbot
	Comment 12 • 9 years ago

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/77cac455dfd92c7fdfea9e5b11e885fb9e2ab068
Bug 1183872 - Improve logviewer layout with a navbar

	Jonathan French (:jfrench) Assignee
	Comment 13 • 9 years ago

Marking fixed per above merge.

	Jonathan French (:jfrench) Assignee
	Comment 14 • 9 years ago

And verified on both stage and prod.