{"action":"closed","issue":{"url":"https://api.github.com/repos/stylelint/stylelint/issues/1132","repository_url":"https://api.github.com/repos/stylelint/stylelint","labels_url":"https://api.github.com/repos/stylelint/stylelint/issues/1132/labels{/name}","comments_url":"https://api.github.com/repos/stylelint/stylelint/issues/1132/comments","events_url":"https://api.github.com/repos/stylelint/stylelint/issues/1132/events","html_url":"https://github.com/stylelint/stylelint/issues/1132","id":150888869,"number":1132,"title":"value-keyword-case complains on font names","user":{"login":"PhiLhoSoft","id":1087902,"avatar_url":"https://avatars.githubusercontent.com/u/1087902?v=3","gravatar_id":"","url":"https://api.github.com/users/PhiLhoSoft","html_url":"https://github.com/PhiLhoSoft","followers_url":"https://api.github.com/users/PhiLhoSoft/followers","following_url":"https://api.github.com/users/PhiLhoSoft/following{/other_user}","gists_url":"https://api.github.com/users/PhiLhoSoft/gists{/gist_id}","starred_url":"https://api.github.com/users/PhiLhoSoft/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PhiLhoSoft/subscriptions","organizations_url":"https://api.github.com/users/PhiLhoSoft/orgs","repos_url":"https://api.github.com/users/PhiLhoSoft/repos","events_url":"https://api.github.com/users/PhiLhoSoft/events{/privacy}","received_events_url":"https://api.github.com/users/PhiLhoSoft/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/stylelint/stylelint/labels/resolution:%20duplicate","name":"resolution: duplicate","color":"cccccc"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-25T14:57:36Z","updated_at":"2016-04-25T15:23:39Z","closed_at":"2016-04-25T15:23:39Z","body":"> Describe the issue. Is it a bug or a feature request (new rule, new option, etc.)?\r\n\r\nBug, spurious warning.\r\n\r\n> Which rule, if any, is this issue related to?\r\n\r\nvalue-keyword-case\r\n\r\n> What CSS is needed to reproduce this issue?\r\n\r\n```css\r\n$mo-font: OpenSans, Verdana, sans-serif; // In a .scss file\r\n// OR just\r\nfont-family: OpenSans, sans-serif;\r\n```\r\n\r\n> What stylelint configuration is needed to reproduce this issue?\r\n\r\n```yaml\r\nrules:\r\n  value-keyword-case: \"lower\"\r\n```\r\n\r\n> Which version of stylelint are you using?\r\n\r\n6.2.1\r\n\r\n> How are you running stylelint: CLI, PostCSS plugin, Node API?\r\n\r\nCLI with `stylelint --syntax scss *.scss`\r\n\r\n> Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?\r\n\r\nNo. Tried with:\r\n\r\n```shell\r\n> stylelint foo.css\r\nfoo.css\r\n 6:15  ×  Expected \"OpenSans\" to be \"opensans\"   value-keyword-case\r\n```\r\n\r\n> What did you expect to happen?\r\n\r\nNo warnings to be flagged, because even if unquoted, font names are not keywords.\r\n\r\n> What actually happened (e.g. what warnings or errors you are getting)?\r\n\r\nThe following warnings were flagged: well, see above!\r\n"}}