|
button { |
|
padding: 15px; |
|
transition: all 1s ease; |
|
user-select: none; |
|
outline: 0; |
|
-webkit-user-select:none; |
|
-webkit-user-drag:none; |
|
background-image: linear-gradient(#DCDCDC, #f6f6f6); |
|
border: 0; |
|
border-radius: 10px; |
|
font-family: 'Roboto', sans-serif; |
|
text-transform: uppercase; |
|
box-shadow: 0px 8px 15px rgba(0, 0, 0, 0.1); |
|
} |
|
button { |
|
background: #F5C518; |
|
border-radius: 0 3px 3px 0; |
|
height: 29px; |
|
vertical-align: middle; |
|
margin-bottom: 10px; |
|
|
|
} |
Styling the button tag differently in different css files is okay for a test project with strictly separated css files, but can quickly get dangerous when your project starts to grow. Before you know it you'll have conflicting css rules and you won't know why it's not working.
It's good to get used to always using (specifically named) classes instead of styling html elements.
BackendCallingApi/public/styles/404.css
Lines 16 to 29 in 830c026
BackendCallingApi/public/styles/styles.css
Lines 104 to 111 in 830c026
Styling the
buttontag differently in different css files is okay for a test project with strictly separated css files, but can quickly get dangerous when your project starts to grow. Before you know it you'll have conflicting css rules and you won't know why it's not working.It's good to get used to always using (specifically named) classes instead of styling html elements.