Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat unknown properties as warnings (not errors) #62

Closed
Jellby opened this issue Nov 20, 2016 · 1 comment
Closed

Treat unknown properties as warnings (not errors) #62

Jellby opened this issue Nov 20, 2016 · 1 comment

Comments

@Jellby
Copy link

Jellby commented Nov 20, 2016

Could we please have an option to treat unknown properties (not detected as vendor extensions) as warnings instead of errors? After all they are perfectly valid, they'll just be ignored if not supported, but warnings are useful in case there's a misspelling.

The following CSS:

h3 {
visibility: none;
adobe-hyphenate: none;
hyphens: none;
-epub-hyphenate: none;
}

should only give an error for visibility: none (unvalid value for valid property), the rest are at most warnings, regardless of the CSS level.

@ylafon
Copy link
Member

ylafon commented Jan 20, 2017

Well, in that case, the invalid value will also be considered as non-existent, so a warning as well.
No errors, just warnings.
Note also that warnings are usually ignored, someone making a typo in a property name will probably never notice it if it is a warning and not an error.

@ylafon ylafon closed this as completed Jan 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants