The errors you are seeing are more likely to be due to a technical error with your .css document. The examples you cite are relative values that are invalid without previously establishing what they relate to. For example, if you are using
em and/or
rem as a value without first establishing a standardized
font-size property then you are using them improperly.
I have not come close to reading all of the documentation they offer to fully explain all elements, but the validator is constantly updated to reflect all current standards. Their documentation is maddeningly detailed.
It is super if you can produce a .css document without errors or warnings but it is fairly normal to have a list of errors and warnings while the .css seems to work as expected. Browsers are far more forgiving than the w3 jigsaw tool. It is intended to help you learn the details and work toward perfection, but nothing happens if you don't. Its purpose is to show you what needs attention.
There is a
nu validator that you can try and it may offer a better explanation of any errors or warnings - it is set up to validate .html, .css and/or .svg files. Select the level of report you want to see: [
validator.w3.org...]
You can read more about any of the terms or elements you are having errors with, though be prepared to open a dozen tabs for any given element as it refers to so many documents that go into increasingly convoluted detail. This page lists "Terms" and you can read more about rem and em usage from here: ht
tps://www.w3.org/TR/css3-roadmap/#terms
The current status of all w3's work is found here: ht
tps://www.w3.org/TR/css3-roadmap/
[edited by: not2easy at 3:33 pm (utc) on Jul 24, 2020]