DOMpurify breaks custom html elements about homebrewery

[calculuschild]

The preferred way to do this is with the curly bracket syntax:

Here is {{myCustomStyle some text}}.

And then the CSS:

.myCustomStyle {
  color: red;
}

Or even:

Here is {{color:red some text}}.

However, your approach should still work. We will look into this.

[ericscheid]

H7 is not a standard html element. Headings are h1 thru to h7.

That said, unrecognised html elements would normally be treated the same as span elements as far as { display: inline; }.

Looking at the html that is rendered into the preview ... and there is no trace of the <h7>.

The unrecognised html has been stripped out. This release has DOMPurify active, which I suspect is causing this.

[marceloabner]

Yeah, my use of headers was useful before on legacy cause typing a header with an autocomplete was quick, but I think using curly brackets is even faster and I keep using the correct standards.

Thanks all for the help and the care in explaining how it works.

[5e-Cleric]

Reopening this to track the actual issue described in the new title