Resharper 8.2 CSS refactoring bug

Hi,

ReSharper is showing the following refactoring suggestion: Requires fallback color

Capture.PNG

But the fallback color is already defined one line before.

4 comments
Comment actions Permalink

Hello Moslem!

In the beginning, there were three ways to specify colors: in hexadecimal format, using either three or six characters, named colors such as

red
, and
rgb()
. CSS3 has since added several new color formats including
rgba()
,
hsl()
, and
hsla()
. While these new color formats bring a remarkable amount of flexibility to how developers define colors and the relationships between them, it can also leave older browsers looking worse than expected.

The problem is that CSS parsers in browsers will skip a property whose name or value is not understood. Older browsers such as Internet Explorer 8 and earlier, do not understand
rgba()
,
hsl()
, or
hsla()
, and as a result will drop any declarations containing them.

For detailed information please refer to https://github.com/CSSLint/csslint/wiki/Require-fallback-colors
0
Comment actions Permalink

Hi,

I totally agree with the fact that a fallback color is required. I am reporting the bug that ReSharper is showing the suggestion although a fallback color is already defined (in the prvious line).

This is only happening with -ms IE specific properties. As you can clearly see -webkit and -moz are handled correctly.

Thanks!

0
Comment actions Permalink

Hello Moslem!

Sorry that missed the point of your message.

Please check that if you hover mouse over -ms-box-shadow it is marked as "Unknown vendor specific extension".
For box-shadow there's no need use -ms prefix cause IE supports box-shadow property (except IE 8, but this is another story).

So it seems that inital issue is caused by using of this prefix.

Thank you.

0
Comment actions Permalink

This issue still exists in R# 2016.2.2.

In .cshtml file:

And in the .css file:





0

Please sign in to leave a comment.