Obviously DevTools are great to have as a dev. But I still think we're in the "C++ template error messages" stage of browser DevTools usefulness. Right now, m

Obviously DevTools are great to have as a dev. But I still think we're in the "C++ template error messages" stage of browser DevTools usefulness. Right now, my DevTools can tell me that a CSS rule is invalid because "15%" is not valid because px or rem are required. But it can't tell me if I'm setting a property in a child that doesn't make sense in the context of where it's used - adding a useless but valid property is just fine. A CSS noob like me really gets very little help from the browser when confronted with something like "wait, why is this element taller than its container?". I can find out the sizes of the elements, and dynamically add styles to change that, and that is great! But that's very much the "PHP expects T_PAAMAYIM_NEKUDOTAYIM" [0] attitude. I get that the browser doesn't care about useless CSS rules generally - but the DevTools really should in order to be useful. [0] https://stackoverflow.com/questions/592322/php-expects-t-paamayim-nekudotayim https://stackoverflow.com/questions/592322/php-expects-t-paa...