[joydaven]

Done

• Removed dangerouslySetInnerHTML from Chip and from the FilterPanelSection heading.
• highlightSubString now returns React nodes with real <strong> elements for matches, so subString emphasis still works while values are rendered as text rather than parsed as HTML. An empty substring now reports match: false; every caller already guards against an empty search term.
• Added tests for substring emphasis, quoted values, markup in values and headings rendering literally, and the utility's escaping. Added a Chip "Substring highlight" story.

Before / after

https://www.loom.com/share/7ed1536ead724322bed8de413f9a82b9

Before: When HTML is entered into the value input box, the output should render it as HTML instead of displaying it as plain text.

QA

Pinging @canonical/react-library-maintainers for a review.

QA steps

• Run yarn docs, open Chip -> Default, set value to <b>bold</b> in Controls: it renders as plain text.
• Open Chip → Substring highlight: the matched letters are bold.
• In the SearchAndFilter story, type part of a section heading: the heading still emphasises it.
• yarn test and yarn lint pass.

Percy steps

One new snapshot for the Chip "Substring highlight" story. No changes to existing stories expected.

Fixes

Fixes: #1091