Closed php-coder closed 6 years ago
I forgot to mention how I'm executing html5validator:
html5validator \
--root src/main/webapp/WEB-INF/views \
--ignore-re 'Attribute “(th|sec|togglz|xmlns):[a-z]+” not allowed' \
'Attribute “(th|sec|togglz):[a-z]+” is not serializable' \
'Attribute with the local name “xmlns:[a-z]+” is not serializable' \
'An "img" element must have an "alt" attribute' \
'The first child "option" element of a "select" element with a "required" attribute' \
--show-warnings
I couldn't reproduce it locally under MacOS. But it 100% reproducible in TravisCi.
Could be related to https://github.com/validator/validator/issues/493
It reproduces on Linux.
@sideshowbarker Could you look at it? I suspect that it's not html5validator problem but rather validator related.
@php-coder I’m not able to reproduce the problem when I directly check the documents using the W3C HTML Checker:
@php-coder Can you link to a Travis build where this error occurred?
@sideshowbarker @svenkreiss Hi, this issue has started to appear again time to time, but now it says that the document in French.
Could you suggest me a way of debugging it? Is enabling verbose mode would help? Where the sources of this check, so I can read it/play with the code? Thanks!
My only suggestion as far as debugging is to see if you can reproduce it with the vnu.jar directly or with https://checker.html5.org/ or https://validator.w3.org/nu/
I agree, you will have to look into the Java part for debugging this.
Also just had a look at your 403.html
file. It actually is a template file and not pure HTML. I wouldn't be surprised if the special characters trip up the language detection.
Also just had a look at your 403.html file. It actually is a template file and not pure HTML. I wouldn't be surprised if the special characters trip up the language detection.
Yeah, if that’s the case, then all bets are off as far as the HTML checker backend behavior goes — and not just specifically for language detection. The checker isn’t a tool for checking pre-parsed PHP or template content. It’s intended for checking the HTML contents as they would be sent over the wire.
It actually is a template file and not pure HTML.
It should be valid HTML that have a bunch of non-standard th:*
attributes.
@svenkreiss Could you add an option to expose --no-langdetect
to html5validator then?
Yes, that sounds like a good idea.
On Thu, Jan 4, 2018 at 6:44 AM, Vyacheslav Semushin < notifications@github.com> wrote:
It actually is a template file and not pure HTML.
It should be valid HTML that have a bunch of non-standard th:* attributes.
@svenkreiss https://github.com/svenkreiss Could you add an option to expose --no-langdetect to html5validator then?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/svenkreiss/html5validator/issues/32#issuecomment-355262481, or mute the thread https://github.com/notifications/unsubscribe-auth/ACpYJpuz_TEyopQwreQcWyUPtNwCLZJjks5tHLmQgaJpZM4M-cg4 .
Version 0.2.10 is now on pypi that has this command line option. Does that help?
Thanks! Looks like it worked!
I see that 0.27 version has started to report the following warnings:
Here are these files: