Fix: extraneous close tags are now reported

Fix: extraneous close tags are now reported

Templates with stray close tags — e.g. `` with more closes than opens — now correctly report each dangling close tag as a validation error (“

start tag is not found.”) in the Problems view and inline in the editor.

This was a long-standing bug inherited from the original WOLips parser: the FuzzyXML close-tag handler had a defensive early return whenever the open-tag stack was empty, which silently swallowed the exact case the validation was meant to catch. An empty stack on a close tag is precisely an extraneous close tag.

Fix: close-tag completion after self-closing tag with parentheses in attribute

Fixed a bug where close-tag completion (Ctrl+Space) would suggest the wrong tag after a self-closing tag whose attribute value started with a delimiter character — typically a parenthesis, like ``. The scanner’s quoted-value tracking lost state when the first character inside the quote was a delimiter, which in turn broke the self-closing pop and left the tag sitting on the unclosed-tag stack. Subsequent close-tag completions would incorrectly suggest closing the stale tag.

Also affects values starting with other delimiter characters (;, +, etc.), not just (.

From the changelog, April 10, 2026.