Beginning to pepper #poobrains templates with <div>s and I'm not sure if I'm doing something wrong…
Since going full force on the #HTML5 semantic tags I've been (successfully) trying to avoid <div> because it offers no semantics.
But I am now beginning to need it for some styling purposes and I'm suspecting that means there's some weakness in either the structure of my HTML or my CSS selectors rather than the <div>s really being needed. 🤔
@phryk although I could recommend css grid and flexbox if you're not using it
@phryk ah was just saying because flexbox and css grids are good for removing unnecessary divs from floating grids :)
@eribloodlust In this case, it's about checkboxes which apparently have all sorts of caveats in different browsers.
For instance CSS for input[type="checkbox]:after doesn't seem to be honored by firefox.
input[type="checkbox]:checked + label gives me even worse problems on chromium…
No clue why all browsers seem to be shitting on form elements… :/
@phryk @eribloodlust if there's a block that has no meaning, and it's there just to make the thing look good in different browsers, IMO <div> is appropriate, nothing wrong about using it.
@eribloodlust My thing already uses flexbox extensively to make the whole thing responsive. I just want the code to be neat and clean, is all. :)