It’s no failure…it’s settings which helps to works correct for all browser (Mozilla etc)
Thread Starter
bamajr
(@bamajr)
If you install this plug-in and activate it, with no content and no changes in the settings, the plug-in FAILS css validation.
I have verified this many times by installing a theme, activating the theme, and then testing css validation to make sure it passes.
Next, I install only your NextGEN plug-in and activate it, and css validation fails. If I disable and delete your plug-in, css validation passes again.
I also reviewed the failures listed in my first post, and they are all CSS code which is found in your plug-in.
those are browser specific css calls
They are not valid standards wise at this time, and will not validate….. HOWEVER, they function in certain browsers and cause no issue in other browsers
They provide a certain functionality, and they work just fine…. but they won’t validate. They are in wide use….
https://developer.mozilla.org/en/CSS/-moz-border-radius
there’s a bunch of stuff around the google. Browser specific css will never validate. But it works. It’s as non-issue really
Thread Starter
bamajr
(@bamajr)
I don’t see the need for the specific css being used, causing the validation to fail. It doesn’t just fail validation in Firefox, but also in IE, Opera, Safari and Chrome. I understand that the W3C CSS validation is for “site-wide” validation, but that is the point of having CSS standards.
What do you loose if you ditch the un-needed css which is causing the validation to fail?
What browser is that code for? It doesn’t seem to effect the plug-in differently for any of the browsers I’ve tested on.
I too really wish that there was a way to get this to validate..bit of a perfectionist and seems a shame that this great plugin causes this issue.
Any plans to change this so it will validate in the next update at all?
Or does anyone know how to get this to validate, would love to know if its possible.
Thanks
Just remove the lines in your css file (the validator show up which files & lines are the problem) and be happy….
This is funny!
Great plugin!
Yup, I don’t get the issue. Now, if the actual code didn’t validate, that’d be an issue.
IMHO, using browser specific css is nice, as long as there is a fail-safe included. Why not enjoy the benefits of browsers just because IE doesn’t play nice?
