Hello,
Just to be clear, what you are saying is that the following issue is a false-positive. Is that correct?
Personally, instead of supporting a custom field that will not often customized, I would prefer that out of the box S4649 ignores font-family
when it’s used in the context of icon fonts.
Today, I see two options:
- hard code a list of well known Icon Fonts (“Font Awesome*”, …) but that would be complex to keep it up to date
- find a way to determine that no issue should be raised if this or that other field is there. For example, if
font-family
is defined without any generic font family but with acontent
field, then nothing should be raised.
Do you see a better way to determine that a CSS block is related to an Icon Font?
Alex