RFE: Validation of hgroup element is based on outdated version of HTML5
Leif Halvard Silli <[email protected]> Sun, 1 Feb 2026 21:50:13 +0100
| Newsgroups | gmane.editors.xxe.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============8917118112273613483==
Content-Type: multipart/alternative;
boundary="------------i4pij05D0aoEkQevVfcubFdg"
Content-Language: nn-NO
This is a multi-part message in MIME format.
--------------i4pij05D0aoEkQevVfcubFdg
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
This code is from the code example from the HTML5 spec:
<hgroup>
<h1>The reality dysfunction</h1>
<p>Space is not the only void</p>
</hgroup>
See: https://html.spec.whatwg.org/multipage/sections.html#the-hgroup-element
The validator in XXE 11 says that <p> is not permitted in that context.
And for the record, <https://validator.nu> says the same thing. Whereas
the Nu validator of W3.org says what the spec says, that it is permitted
- <https://validator.w3.org/nu/#textarea>
So I suggest that you update the validator in XXE to be in accordance
with the spec.
For history, the <hgroup> element used to permit one or more h1-h6
elements. Whereas the current spec says
* «Zero or more p elements, followed by one h1, h2, h3, h4, h5, or h6
element, followed by zero or more p elements»
It seems like engine behind validator.nu is several versions behind the
version at validator.w3.org/nu – the old engine expect only h1-h6
elemenbts, whereas the new engine is in accordance with the spec. And it
seems the validator inside XXE has the same issue - it accepts only
h1-h6 elements.
Leif Halvard Silli
--------------i4pij05D0aoEkQevVfcubFdg
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>This code is from the code example from the HTML5 spec:</p>
<p><hgroup><br>
<h1>The reality dysfunction</h1><br>
<p>Space is not the only void</p><br>
</hgroup></p>
<p>See:
<a class="moz-txt-link-freetext" href="https://html.spec.whatwg.org/multipage/sections.html#the-hgroup-element">https://html.spec.whatwg.org/multipage/sections.html#the-hgroup-element</a></p>
<p>The validator in XXE 11 says that <p> is not permitted in
that context. And for the record, <a class="moz-txt-link-rfc2396E" href="https://validator.nu"><https://validator.nu></a>
says the same thing. Whereas the Nu validator of W3.org says what
the spec says, that it is permitted -
<a class="moz-txt-link-rfc2396E" href="https://validator.w3.org/nu/#textarea"><https://validator.w3.org/nu/#textarea></a></p>
<p>So I suggest that you update the validator in XXE to be in
accordance with the spec.</p>
<p>For history, the <hgroup> element used to permit one or
more h1-h6 elements. Whereas the current spec says </p>
<ul>
<li>«Zero or more p elements, followed by one h1, h2, h3, h4, h5,
or h6 element, followed by zero or more p elements»</li>
</ul>
<p>It seems like engine behind validator.nu is several versions
behind the version at validator.w3.org/nu – the old engine expect
only h1-h6 elemenbts, whereas the new engine is in accordance with
the spec. And it seems the validator inside XXE has the same issue
- it accepts only h1-h6 elements.</p>
<p>Leif Halvard Silli</p>
</body>
</html>
--------------i4pij05D0aoEkQevVfcubFdg--
--===============8917118112273613483==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
--===============8917118112273613483==--