4 ms·
because there is no error. there is no way for the browser to know that the css you wrote is not the css you wanted.
by gfxgirl 5y ago
because there is no error. there is no way for the browser to know that the css you wrote is not the css you wanted.
- tiborsaas 5y agoThe browser does know if there's an error. The devtools will tell you if a property is invalid.
- gfxgirl 5y agoThe problem is almost never that the CSS you wrote has a syntax error. The problem is almost always the CSS with no syntax errors you wrote isn't doing what you wanted it to do. The browser doesn't know what you wanted it to do so it can't help you.
- tiborsaas 5y agoThat's obviously true, the browser just blindly interprets the rules. However, sometimes spec changes or solidifies in a way that can break existing code so there are other cases to consider. There's also tooling to catch these errors if it really matters.