Stylus: two bugs

[catcat520]

same css code in stylish and stylus
then stylus error tips : Expected end of value but found ','.
and still can not supports property 'unicode-range'.

code,kbd,pre,samp,tt,var{font-family:"/*NoForceAllFonts By/Microsoft YaHei","HighLevelEmoji","Catcat520.Lite.Latin","SDF.TypeSetCtrlFonts","SDF.CnSymbol","SDF.EnSymbol","SDF.Number","此处填写英文字体","此处填写font-family的名称","EnFonts@VrFonts","SysPro2Mono@VrFonts","SysPro@VrFonts", "Microsoft YaHei UI@VrFonts","Microsoft YaHei@VrFonts","Microsoft JhengHei UI@VrFonts","Microsoft JhengHei@VrFonts","PingFang SC@VrFonts","PingFang TC@VrFonts","PingFang HK@VrFonts","Noto Sans CJK SC@VrFonts","Noto Sans CJK TC@VrFonts","Noto Sans CJK JP@VrFonts","Noto Sans CJK K@VrFonts","Source Han Sans SC@VrFonts","Source Han Sans TC@VrFonts","Source Han Sans@VrFonts","Source Han Sans K@VrFonts","SimSun@VrFonts","Hiragino Sans GB@VrFonts","WenQuanYi Micro Hei@VrFonts","WenQuanYi Zen Hei@VrFonts","LowLevelEmoji","Segoe UI Symbol","Segoe UI Historic","Symbola","Quivira","Meiryo@VrFonts","Malgun Gothic@VrFonts","MingLiU@VrFonts","MingLiU_HKSCS@VrFonts","SimSun-ExtB","MingLiU-ExtB","MingLiU_HKSCS-ExtB","Nimbus Roman No9 L","Droid Sans Fallback","Symbol","FZSongS","Simsun (Founder Extended)","Microsoft Himalaya","Microsoft New Tai Lue","Microsoft PhagsPa","Microsoft Tai Le","Microsoft Uighur","Microsoft Yi Baiti","Mongolian Baiti","Estrangelo Edessa","Ebrima","Euphemia","Nyala","Plantagenet Cherokee","sylfaen","Arial Unicode MS","Code2000","HanaMinA","HanaMinB","Unifont" !important;}

[catcat520]

[narcolepticinsomniac]

Those are warnings, not errors. CSSLint is far from perfect, unfortunately. The reason for the discrepancy between Stylus/Stylish is that our CSSLint was updated to the latest version. The latest version has a lot of improvements, but false positives still exist. In general, if you know that the warnings/errors are false positives, simply ignore them.

The "unicode-range" warning occurs in both Stylus/Stylish. The "font-family" warning, which only occurs in Stylus, seems to be caused by the parentheses in "Simsun (Founder Extended)".

Again, if you know better than the linter and the code functions normally, warnings and errors can be ignored. I know CSSLint still throws errors for variables because they haven't been accounted for.

I believe Stylus implements some hacks for compatibility, but it'd be up to @schomery if something like this qualifies.

[schomery]

@catcat520 the unicode-range warning is now muted https://github.com/schomery/stylish-chrome/commit/55fd65471363967510c9b700e17e34cba8deaaf6

If anybody wants to play with warnings take a look at
https://github.com/schomery/stylish-chrome/blob/master/codemirror-overwrites/addon/lint/css-lint.js#L37-L51

https://github.com/schomery/stylish-chrome/issues/10#issuecomment-278778135

@narcolepticinsomniac the hsl color code warning is also muted;
https://github.com/schomery/stylish-chrome/blob/master/codemirror-overwrites/addon/lint/css-lint.js#L43

[catcat520]

@narcolepticinsomniac @schomery
thank you very much

[narcolepticinsomniac]

@schomery Good stuff! Still not muting the same warnings for hsla though, which would be nice.

[schomery]

@narcolepticinsomniac the new commit should support both hsl and hsla

[narcolepticinsomniac]

Nice! Working well.