Testing strong and bold tags

Looking to fix a bug in the FrogFind site simplifier code. (Direct link to when passed through FrogFind.; FrogFind's GitHub page.) A modern browser shouldn't have any of the "normal text" below rendered in bold or italics. 2023-07-03, go to the index.

This paragraph has a plain tag, without attributes.

This paragraph has neither nor tags in it. It should not appear bold. (1)

This paragraph has a plain tag, without attributes.

This paragraph has neither nor tags in it. It should not appear bold. (2)

This paragraph has a tag with three attributes: class=foo lang=en id=p6, plus that code tag.

This paragraph has neither nor tags in it. It should not appear bold. (3)

This paragraph has a tag with three attributes: class=foo lang=en id=p8, plus that code tag.

This paragraph has neither nor tags in it. It should not appear bold. (4)

All the previous paragraphs had their tags closed appropriately: closes and closes . Here I now place a few extra closing tags to counteract any closing strong tags inadvertently turned into closing bold tags: [1] [2].

Now, the same thing with and tags, but more succintly:

em-without-attributes. Normal text A. i-without-attributes. Normal text B. i-with-three-attributes. Normal text C. em-with-three-attributes. Normal text D. Extra closing tags: [1] [2].

One thing left: the <code>, <samp> and <kbd> elements. By default, all three should display in monospace.

Code without attributes. Normal text A. Kbd without attributes. Normal text B. Samp without attributes. Normal text C.
Code with three attributes. Normal text D. Kbd with three attributes. Normal text E. Samp with three attributes. Normal text F. Extra closing </code> tags: [1] [2] [3].

Here's a <pre> tag, with one space-indented line and one tab-indented line, the tab being encoded in the source with an 	 entity:

First unindented line.
    Second indented line, with four spaces.
	Third indented line, with one tab.

This paragraph is not part of the <pre> element: it should be on a line of its own.

This bit is in a blockquote. It should be indented a bit.

Immediately when testing I found a first bug: HTML in the head's <title> element was interpreted and put into an <h1> element at the very top of the page, turning everything bold. (The title used to be "Testing and <bold> tags", but I took the angle brackets out to avoid this.) The original page doesn't have a <h1> element in it in the first place.

Also turns out that the FrogFind renderer doesn't do anything with <code> or <pre> – it just removes all of them. No monospace in 1990?

Additional discoveries of the current renderer:

<hr> tags are removed entirely.
An – entity I had – here are a few more – was turned into a plain ASCII hyphen. Here's also an &mdash: —. Here they are as actual Unicode characters: –en– —em—. ← → ↑ ↓
Here's a whole row of named character entities; it should be those that existed way back when in the IE6 days, or mainly the Windows-1252 character set. I didn't include the much newer stuff like &Yacy; and such.
" & ' < > ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ × ÷ À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö Ø Ù Ú Û Ü Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ø ù ú û ü ý þ ÿ Ÿ Œ œ Š š Ž ž Č č ƒ ˆ ˜ Α Β Γ Δ Ε Ζ Η Θ Ι Κ Λ Μ Ν Ξ Ο Π Ρ Σ Τ Υ Φ Χ Ψ Ω α β γ δ ε ζ η θ ι κ λ μ ν ξ ο π ρ ς σ τ υ φ ϕ χ ψ ω ϑ ϒ ϖ ( ) ( ) ( ) – — ― ‘ ’ ‚ “ ” „ † ‡ • … ‰ ′ ″ ‹ › ‾ ⁄ € ℑ ℘ ℜ ™ ℵ ← ↑ → ↓ ↔ ↵ ⇐ ⇑ ⇒ ⇓ ⇔ ∀ ∂ ∃ ∅ ∇ ∈ ∉ ∋ ∏ ∑ − ∗ √ ∝ ∞ ∠ ∧ ∨ ∩ ∪ ∫ ∴ ∼ ≅ ≈ ≠ ≡ ≤ ≥ ⊂ ⊃ ⊄ ⊆ ⊇ ⊕ ⊗ ⊥ ⋅ ⌈ ⌉ ⌊ ⌋ ⟨ ⟩ ◊ ♠ ♣ ♥ ♦ ˙ №
A plain tag – which is legal in HTML5, and I believe the recommended way of writing it – is made to be followed by a closing tag. This closing tag shouldn't be a thing; tags don't contain anything. In my modern browser (Firefox version 100-something), this closing tag is also rendered like an extra , so in essence all s are doubled. I had to specifically use the immediately-closed version. Here's the normal, slashless one:
There shouldn't be an empty line between this one and the above one. And here's the one with the slash in it:
There shouldn't be an empty line above this either.
The instantly-closed doesn't work: it also is turned into a pair of tags, , and it looks horrible on a modern browser.
Does the FrogFind renderer allow the weird, fun and deprecated old tags, like ? This line should be in red, purple, red, green and brown.