[solved] HTML minifier errors with unclosed <p> tags?

[anaxite]

I'm getting HTML minifier warnings with our documentation, but I wanted to check whether I'm experience intended behavior before creating a new issue.

(TL;DR: does the HTML minifier trip up on unclosed but valid <p> tags?)

I installed the docusaurus-openapi-docs plugin to help document our API. When building our site with pages generated by the plugin, I get this warning for every plugin-generated page:

  - [HTML minifier diagnostic - error] No "p" element in scope but a "p" end tag seen - {"primary_spans":[{"end":21374,"start":21370}],"span_labels":[]}

I checked an un-minified documentation build; <p> tags are only in two locations, and the pages leave them unclosed if they have content, like this example:

<p>Returns the number of root records for the query.<br><p>Description of {query}: ?<p></p>

(which would ventilate like this:)

<p>Returns the number of root records for the query.<br>
<p>Description of {query}: ?
<p></p>

Could this be tripping up the minifier, and if so, is this behavior intended? I don't see <p> tags used like this much, but this use of the tag is apparently valid and it does not need to be closed if it precedes certain other elements.

[slorber]

It's not possible to help you without a repro. At least share the MDX doc that cause trouble.

Also make sure to use an up to date plugin version, see also:

• Docusaurus v3.6 - enable Docusaurus Faster PaloAltoNetworks/docusaurus-openapi-docs#1003 (comment)
• Address HTML minifier warnings caused by malformed MDX and HTML PaloAltoNetworks/docusaurus-openapi-docs#1033

If the lib still produces warning, you should report to them with a clear minimal repro so that they can fix the warnings.

Also double check that it's not your own code producing those warnings. Nesting <p> one into the other is not valid HTML.

I explain how to troubleshoot these warnings here: #10580

[anaxite]

I can't share the original files. I'll try and get the warnings to appear with some fictional data.

[slorber]

You can likely replace all sensitive content by lorem ipsum until, and remove things until the warning disappear to identify the problematic section. Then paste that section in the MDX playground to see how it is compiled by MDX (see guide here: #10580)

[anaxite]

Thanks for your comment ; I was able to find the problem. It's not Docusaurus, it's not the plugin, it's entirely due to someone putting malformed HTML data in an OpenAPI file.

All is normal.