Error console gets spammed with CSS warnings. about mpkedit

[bryc]

Those seem to be CSS warnings, not JS warnings. I have those messages disabled in the console because they're really common. Every webpage has 'em - it's when a CSS property is used that the browser doesn't understand. Font Awesome uses a lot of cross-browser code to maximize browser support. The progid stuff is specific to IE for example.

It shouldn't cause any problems because the browser simply ignores it - that's why multiple vendor specific properties can be used, like -o-x, -webkit-x and -moz-x. Firefox will obviously not recognize the Opera or Webkit properties. To be honest I'm surprised there's only 6 of these.

[cxd4]

lol! CSS warnings sorry, not JS. Ate so much JS for breakfast and lunch I just said JS without even looking at the console actually. (I did look at the code it highlighted, but it was all cramped together into a single line and I just tl;dr'd it as JS.)

Well I guess my OCD was hoping there would be a way to modify the CSS to prevent the warnings from buffering up the console RAM, but if it can't be done without either replacing Font Awesome entirely or using something different, then maybe the issue can't be helped.

[bryc]

Unfortunately not without potentially breaking IE or OS X things. Why not just disable CSS warnings?

I did modify the original font-awesome.min.css to remove WOFF2 fonts, because it was trying to load fonts that didn't exist (404 error), when I only had WOFF (original) fonts. I deleted all but the *.woff fonts from the package.

[cxd4]

I personally am not really a "disable warnings" kind of guy. When it comes to clean performance/well-defined reactions, I always like to go straight for the source to maximize consistent, direct behavior.

However I understand it that there's nothing otherwise that can be done in this case without writing something in place of Font Awesome, so I ought to spare you the potential distraction and I think just close the issue.