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

Width: unset not showing as unsupported by IE #9

Closed
ZacharyRSmith opened this issue Apr 18, 2017 · 3 comments
Closed

Width: unset not showing as unsupported by IE #9

ZacharyRSmith opened this issue Apr 18, 2017 · 3 comments

Comments

@ZacharyRSmith
Copy link

I ran stylelint with width: unset as a CSS rule, but the linter did not warn me about this, even though it was warning me about other things not supported by IE.

CanIUse shows unset as being unsupported by IE.

@ismay
Copy link
Collaborator

ismay commented Apr 18, 2017

If you're seeing other warnings then I suspect it's a doiuse issue (which we use to detect browser support). Try using only doiuse (without stylelint) and see if that yields the same results. If it does it's a doiuse issue and you can open an issue there. Otherwise let me know and we'll reopen and investigate further (a reduced testcase would be nice in that case).

@ismay ismay closed this as completed Apr 18, 2017
@ZacharyRSmith
Copy link
Author

For future reference:

My workaround:

I'm using stylelint to run doiuse, in addition to other linting. To warn about "initial" and "unset", I have the below rule in my .stylelintrc. The built-in rule 'declaration-property-value-blacklist' blacklists the property-value pair I give it. The pair I give it is:

property: "/^.*/" (match all regex)
value: ["initial", "unset"]

So, all properties with a value of "initial" or "unset" will throw a violation.

I set the violation severity to warning.

		"declaration-property-value-blacklist": [{
			"/^.*/": ["initial", "unset"]
		}, { "severity": "warning" }],

@ismay
Copy link
Collaborator

ismay commented Apr 19, 2017

Thanks @ZacharyRSmith. Also, I'll quote your other comment for others encountering this issue:

From what I can tell looking at the [doiuse] source code, no unsupported values are being checked -- only unsupported properties.

So this has to do with doiuse, which is wrapped by this lib. See this issue: anandthakker/doiuse#56

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