3 ms·
Yep ! This is the huge problem with css and «meaningful» selectors, no matter how much you try to make things clear, nuances and details fades and you end up go
by tuyiown 3y ago
Yep ! This is the huge problem with css and «meaningful» selectors, no matter how much you try to make things clear, nuances and details fades and you end up going back end forth between css code, inspector and HTML to figure out what's happening.
Utility based css selectors that do one and single thing are clear and explicit, removing most (but not all) that hassle.
- tipiirai 3y agoNot all developers have experienced these problems. There are people who prefer the semantic approach. I'm definitely one.
- aloisdg 3y agoNot all team are homogeneous. go for the friction less solution.
- HelloNurse 3y agoI strongly doubt a reasonably designed "semantic" design can be half-forgotten after taking a break; the fine points of the implementation of sophisticated rules (e.g. why did we put the left border on the parent and the right border on the child) might suffer from obsolescence and lack of documentation, but the markup structure and the names should be obvious. Forgetting what plethora of non-semantic classes should be used on what elements seems a far more likely problem.
- tuyiown 3y agoYes, there are conditions of people and project where you can avoid those. But they a are plenty of situation when it becomes too hard, such as when you can't constraint a designer to your implementation details, or that same semantic concepts have different UI cases.