To be more precise: All pictures, used in captcha have incorrect xmlns attribute.
Here is error from validator: Bad value https://www.w3.org/2000/svg for the attribute xmlns (only http://www.w3.org/2000/svg permitted here).
xmlns – is not actual url to be used somewhere, but actually name for scheme, so it should be used as is.
You could check it in SVG specification: https://www.w3.org/TR/SVG/intro.html
Hi,
Thank you for bringing this to my attention.
The SVGs used in the plugin have been minified to reduce file size, I have not seen validation errors in the past using the compression tool.
I am currently working on version 3.3, I will look into the validation errors.
Hello,
After looking into the issue I found that the SVG formatting passes the W3 validator.
When I passed the SVG code into the validator by itself I get two warnings (not errors), those warnings go away when the SVG is used within the HTML document.
While reading the SVG documentation you suggested, I found that the current SVG structure used in the plugin is correct, so long as its used as HTML which is how the plugin is using it.
I can see w3 validator errors with this scheme urls, e.g. https://validator.w3.org/nu/?doc=https%3A%2F%2Fdev.nixys.ru
This site uses latest versions of Contact Form/Contact Form Image Capture plugins.
It show error:
Error: Bad value https://www.w3.org/2000/svg for the attribute xmlns (only http://www.w3.org/2000/svg permitted here).
e=”bot” /><svg width=”50″ height=”50″ aria-hidden=”true” role=”img” xmlns=”https://www.w3.org/2000/svg” viewBox=”0 0 576 512″><path
and warning:
Warning: Attribute xmlns is not serializable as XML 1.0. for the same tag.
If I replaced https to http manually, errors and warnings disappeared.
Interesting, those errors never appeared in the validation tests I performed.
It looks to be an issue primary between “http” vs “https”.
I will correct this in the next update.
I have released an update to fix the issue, please update to version 3.3.1.
Thank you for fast response and fix, it validates perfectly now!
