comparison mercurial/templates/static/style-monoblue.css @ 35530:acd8a2454b47

monoblue: make actual changeset entries have backgrounds on /graph

This patch removes a separate container for backgrounds only and puts
backgrounds on changeset elements themselves. This makes it so that JS code
doesn't need to create background elements separately anymore.

There's a bit of manipulating positions of elements: every changeset entry has
a "fg" element that gets a higher z-index than <canvas> element. This
prioritizes text information, so that even if it somehow gets close to the
graph drawn on <canvas> (which has z-index of 5), it'll still be on top of it.
This can happen if commit message has a long first line and browser window is
narrow, for example.

'parity' is added to each entry because there's no stripes2 class in monoblue,
only in paper.

35529:5afe0ca59b07

	position: absolute;
	z-index: 5;
	top: -0.7em;
}

ul#nodebgs li.parity0 {
    background: #F1F6F7;
}

ul#nodebgs li.parity1 {
    background: #FFFFFF;
}

ul#graphnodes {
	position: absolute;
	z-index: 10;
	top: 7px;
	list-style: none inside none;
}

ul#nodebgs {
	list-style: none inside none;
}

ul#graphnodes li, ul#nodebgs li {
	height: 39px;
}

ul#graphnodes li .info {
	margin-top: 2px;
}

35530:acd8a2454b47

	position: absolute;
	z-index: 5;
	top: -0.7em;
}

ul#graphnodes li.parity0 {
    background: #F1F6F7;
}

ul#graphnodes li.parity1 {
    background: #FFFFFF;
}

ul#graphnodes {
	list-style: none inside none;
	margin: 0;
	padding: 0;
}

ul#graphnodes li {
	height: 37px;
	overflow: visible;
	padding-top: 2px;
}

ul#graphnodes li .fg {
	position: absolute;
	z-index: 10;
}

ul#graphnodes li .info {
	margin-top: 2px;
}