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

vs code gives warning about modern-normalize #67

Open
mu-us61 opened this issue Nov 12, 2022 · 4 comments
Open

vs code gives warning about modern-normalize #67

mu-us61 opened this issue Nov 12, 2022 · 4 comments

Comments

@mu-us61
Copy link

mu-us61 commented Nov 12, 2022

I dont know if this is really an issue or not, but nonetheless kind of distracting warnings

image

@scheinercc
Copy link

Not an issue. Checking the VSCode documentation, you could to turn off CSS validation for your workspace in order to not get these warnings anymore: https://code.visualstudio.com/Docs/languages/CSS#_syntax-verification-linting

@Emkas
Copy link

Emkas commented Apr 20, 2023

Off course there are non standard properties... This is what this library is about.

More distracting is that this issue is open for a half a year.

@ghost
Copy link

ghost commented Jul 29, 2023

Is it okay to add the standard properties VS is asking for with the same value as the one highlighted?
I did that with mine and it stopped giving me warnings. VS told me to add the standard property as to maintain compatibility. This may even be added to the code in the future. I'm just a newbie though. Hope to get some feedback.

This was the change I did.

button,
[type='button'],
[type='reset'],
[type='submit'] {
	-webkit-appearance: button;
	appearance: button; /* Added line */
}

[type='search'] {
	-webkit-appearance: textfield; /* 1 */
	appearance: textfield; /* Added line*/
	outline-offset: -2px; /* 2 */
}

@Rafagd
Copy link

Rafagd commented Aug 17, 2023

The idea is to use the non-standard properties to fix stuff only on the browsers that need fixing.
That is why they are not using the standard properties.

Just ignore the VS errors or exclude this file from VS checking.
These non-standard properties are intentional and quite frankly the whole point of these libraries.

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

4 participants