suggestion: Consider including whiteSpace: "pre-wrap", to maintain existing white space. We take this approach in CodeBlock when we need to wrap lines.

this sounds reasonable, but I double-checked with two models in Cursor and they seem to suggest otherwise. I will probably try it in another PR and see if our test run through.

I reviewed our Markdown container styles and how CodeBlock handles wrapping.

• Yes for CodeBlock/inline code: using whiteSpace: "pre-wrap" makes sense where we intentionally preserve whitespace.
• Not for general Markdown container: applying whiteSpace: "pre-wrap" on StyledStreamlitMarkdown would inherit into p, li, td, etc., preserving sequences of spaces and single newlines. That changes standard Markdown rendering (which normally collapses whitespace) and risks layout regressions. For the long-word overflow fix, overflowWrap: "break-word" at the container plus existing p: { wordBreak: "break-word" } already addresses the issue without changing whitespace semantics.

Answer: It makes sense in code contexts (which we already do), but adding whiteSpace: "pre-wrap" globally to Markdown would likely break existing behavior. I recommend keeping the current change as-is.

Another model:

Do not add whiteSpace: "pre-wrap" globally. We already preserve whitespace where intended (inline code, <pre>). If you need even more aggressive breaking of long tokens, consider overflowWrap: "anywhere" instead of changing whitespace behavior.