Read on Twitter
It has been a long time since I& #39;ve done any web development. Back then, table layouts were everywhere, and there was movement towards semantic HTML.
Looking through some UI frameworks (bootstrap et al), it& #39;s interesting to see that said movement completely and utterly failed.
Looking through some UI frameworks (bootstrap et al), it& #39;s interesting to see that said movement completely and utterly failed.
I mean, maybe there& #39;s a reason for it. Maybe
```
<nav class="navbar">
<ul class="navbar-nav">
<li class="nav-item">...
</ul>
<nav>
```
makes sense?
Also, perhaps nesting of <div>s ad-nausium is ok.
But it feels like nothing was learned. Please tell me I& #39;m wrong.
```
<nav class="navbar">
<ul class="navbar-nav">
<li class="nav-item">...
</ul>
<nav>
```
makes sense?
Also, perhaps nesting of <div>s ad-nausium is ok.
But it feels like nothing was learned. Please tell me I& #39;m wrong.
There also used to be a general rule that a class should convey meaning, not styling, unless that style was complex. So THIS???
```
.text-center {
text-align: center !important;
}
```
This must be one of those "I heard using the style attribute is bad" moments. It has to be.
```
.text-center {
text-align: center !important;
}
```
This must be one of those "I heard using the style attribute is bad" moments. It has to be.
OH MY LORD I JUST FOUND OUT THAT <input> TAGS NEED "form-control" CLASS AND I JUST LOST MY SHIT.
I mean... I guess it makes sense to make the style apply to sections of the page, to prevent other components from being infected. But WHY NOT JUST ADD IT AS A CLASS TO THE FORM!?
I mean... I guess it makes sense to make the style apply to sections of the page, to prevent other components from being infected. But WHY NOT JUST ADD IT AS A CLASS TO THE FORM!?
