html5 living standard validation of "picture" element

[olafberg]

I am currently developing/implementing an xslt from TEI-P5 to a HTML5 Website. I want to integrate some pictures and the html-template that I got from the webdesigner uses the <picture> Element, defined in HTML5 Living Standard https://html.spec.whatwg.org/multipage/ ... re-element used to deliver different solutions of one image depending on the pixel of the web browser frame. Oxygen validates this element as error, and as a side effect it does not indent correct the elements used around the use of the picture Element.
Is it possible to include this element into the validation by customizing some defaults? If possible: how should I do this?

By the way: Oxygen validates also two entries as error, that our web designer put in the head:
<meta http-equiv="x-ua-compatible" content="ie=edge"/>
<link rel="apple-touch-icon" sizes="180x180" href="files/icons/apple-touch-icon.png"/>
It seems to me that the link rel entry is not official standard but the designer says it is helpful for display on apple hardware. II would be happy if it would be possible to include these entries as well as valid in the oxygen validation.

[teo]

Hello and thank you for the feedback!

I think the problem is due to the following fact:
- the HTML file generated by the transformation is actually an XHTML file (i.e. it contains an XHTML namespace declaration: xmlns = "http://www.w3.org/1999/xhtml")
- Oxygen automatically detects the XHTML content type of this file and the automatic validation is done with JING engine which is based on a set of specific schemas.

I remember there was a discussion between our team members, whether to automatically validate XHTML documents with HTML W3C Validator, or not. For reasons of backward compatibility mainly, we decided not to do so. But maybe we will reconsider this aspect, given the feedback received from you.

Anyway, to proper validate the (X)HTML file generated by the transformation according to your specific needs, you could proceed as follows:
- create a custom validation scenario (choose Configure Validation Scenario option from Validate toolbar menu button)
- in Validation Engine field the default proposal should be W3C HTML Validator this time
- leave it so, and save or apply this validation scenario directly.

The validation errors you mentioned should no longer be reported this time. However, other types of errors may be reported on this occasion, once the validation engine has changed.