appengine/cmd/milo/frontend/static/buildbot/css/default.css - Issue 2086353004: milo: put line breaks between step text strings

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: appengine/cmd/milo/frontend/static/buildbot/css/default.css

Issue 2086353004: milo: put line breaks between step text strings (Closed) Base URL: https://chromium.googlesource.com/external/github.com/luci/luci-go@master

Patch Set: milo: put line breaks between step text strings Created 4 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « appengine/cmd/milo/frontend/expectations/buildbot-buildbot.TestableBuild-Debug_page-_CrWinGoma_30608.html ('k') | appengine/cmd/milo/frontend/templates/bootstrap/pages/build.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 /* Copyright 2015 The LUCI Authors. All rights reserved.	1 /* Copyright 2015 The LUCI Authors. All rights reserved.

2 * Use of this source code is governed under the Apache License, Version 2.0	2 * Use of this source code is governed under the Apache License, Version 2.0

3 * that can be found in the LICENSE file.	3 * that can be found in the LICENSE file.

4 */	4 */

5	5

6 body.interface {	6 body.interface {

7 margin-left: 30px;	7 margin-left: 30px;

8 margin-right: 30px;	8 margin-right: 30px;

9 margin-top: 20px;	9 margin-top: 20px;

10 margin-bottom: 50px;	10 margin-bottom: 50px;

(...skipping 681 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
692 }	692 }

693	693

694 form.command_forcebuild .force-nested > .label {	694 form.command_forcebuild .force-nested > .label {

695 font-weight: bold;	695 font-weight: bold;

696 display: list-item;	696 display: list-item;

697 }	697 }

698	698

699 form.command_forcebuild .force-any .force-text {	699 form.command_forcebuild .force-any .force-text {

700 display: inline;	700 display: inline;

701 }	701 }

	702

	703 div.step-text:first-child {
	Ryan Tseng 2016/06/23 00:45:35 This feels like a hack ... But oh well, might be b This feels like a hack ... But oh well, might be better than the <br> hackery, I'm not actually sure whats idiomatic. nodir 2016/06/23 01:04:39 Specifying how stuff should look like in CSS shoul Show quoted text On 2016/06/23 00:45:35, Ryan Tseng wrote: > This feels like a hack ... But oh well, might be better than the <br> hackery, > I'm not actually sure whats idiomatic. Specifying how stuff should look like in CSS shouldn't be hackery? It is CSS's purpose,t but I'm not a frontend dev
	704 display: inline;

	705 }

OLD	NEW