Since the latest js visual composer update massive amounts of warnings and errors now appear after I had zero errors which took me a long time to do.
One update has ruined months of work.
type='text/javascript' -> massive amounts of warnings stating type= is no longer supported.
the w3c html validator is also coming up with errors for css. This is not the css validator but the html validator being used.
background-clip: text
Property text-fill-color doesn't exist
and
font size
and
negative line-height errors
Went from not one warning or error to over 100 errors and warnings
Yes, these items may be new or getting deprecated but please write this up and test it and also tell me when this will be fixed or what files I can fix these up manually in as this is really, really poor for from upgrade to upgrade having this occur.
This should be stated in the fixes and issue release problems.
Please explain how to fix and what methods you use in testing before release to make sure html compliance.
Since the latest js visual composer update massive amounts of warnings and errors now appear after I had zero errors which took me a long time to do.
One update has ruined months of work.
type='text/javascript' -> massive amounts of warnings stating type= is no longer supported.
the w3c html validator is also coming up with errors for css. This is not the css validator but the html validator being used.
background-clip:
textProperty
text-fill-colordoesn't existand
font size
and
negative line-height errors
Went from not one warning or error to over 100 errors and warnings
Yes, these items may be new or getting deprecated but please write this up and test it and also tell me when this will be fixed or what files I can fix these up manually in as this is really, really poor for from upgrade to upgrade having this occur.
This should be stated in the fixes and issue release problems.
Please explain how to fix and what methods you use in testing before release to make sure html compliance.
Thanks for the Info . Have noted to have the developer look into this.
Unfortunately we dont have a ETA of when this will be looked into .
Be.st
ThemeNectar Support Team
I went looking for a solution at least to the css issue.
I found that when I went and changed the style sheet to be external in the Salient settings that this removed the bug.
I believe you have a scenario where useless css gets put in the style sheets.
If I have not activated woocommerce for example there should be no css for it yet I am finding css activated for it.