feature/MAPG-235-basic-challenge-mode #48
@ -75,11 +75,6 @@ div.mapItem>div.buttonContainer {
|
|||||||
grid-auto-flow: column;
|
grid-auto-flow: column;
|
||||||
}
|
}
|
||||||
|
|
||||||
#restrictions {
|
|
||||||
margin-top: 1em;
|
|
||||||
margin-bottom: 1em;
|
|
||||||
}
|
|
||||||
|
|
||||||
#restrictions input {
|
#restrictions input {
|
||||||
balazs marked this conversation as resolved
Outdated
|
|||||||
height: auto;
|
height: auto;
|
||||||
margin: 0.5em;
|
margin: 0.5em;
|
||||||
|
@ -43,7 +43,7 @@ TODO: condition!
|
|||||||
<p class="bold center marginTop marginBottom">OR</p>
|
<p class="bold center marginTop marginBottom">OR</p>
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<div id="restrictions">
|
<div id="restrictions" class="marginTop marginBottom">
|
||||||
<h3>Optional restrictions</h3>
|
<h3>Optional restrictions</h3>
|
||||||
<div>
|
<div>
|
||||||
<div>
|
<div>
|
||||||
|
Loading…
Reference in New Issue
Block a user
I think some of the rules should be handled on higher level, for example
font-family
in mapguesser.css line 34,margin-top
andmargin-bottom
could be handled by classesmarginTop
andmarginBottom
, etc.But it is fine for now because some rules would require refactoring (for example for inputs).