HTML API: Expose self-closing flag in Tag Processor

[dmsnell]

Introduce has_self_closing_flag() to the HTML Tag Processor, exposing whether a currently-matched tag contains the self-closing flag /, used when determining if one needs to look for a closing tag of the same name.

This enables structural parsing of an HTML document and is needed to identify self-closing HTML foreign elements.

Introduce has_self_closing_flag() to the HTML Tag Processor, exposing whether a currently-matched tag contains the self-closing flag /, used when determining if one needs to look for a closing tag of the same name.

This enables structural parsing of an HTML document and is needed to identify self-closing HTML foreign elements.

Trac ticket #58009

cc: @adamziel @gziolo @ockham

LGTM! I left two minor notes but nothing big.

[Bernhard Reiter]

In 55619:

HTML API: Add has_self_closing_flag() to Tag Processor.

In this patch we're adding has_self_closing_flag() to the HTML Tag Processor.
This exposes whether a currently-matched tag contains the self-closing flag /.

This information is critical for the evolution of the HTML API in order
to track and parse HTML structure, specifically, knowing whether an
HTML foreign element is self-closing or not.

Props dmsnell, zieladam.
Fixes #58009.

Committed to Core trunk in r55619.

[kebbet]

Should this ticket be milestoned, instead of Awaiting review? Should this be backported to 6.2.1?

[Bernhard Reiter]

Replying to kebbet:

Should this ticket be milestoned, instead of Awaiting review? Should this be backported to 6.2.1?

Thanks for the ping, and apologies for missing this! 6.3 should be fine -- I've now set the milestone accordingly!