I-Beam headers have undesirable wrapping

[FionaDyalog]

The code element of the header should not wrap.

For example, see https://dyalog.github.io/documentation/20.0/language-reference-guide/the-i-beam-operator/enable-compression-of-large-components/

On this page, as you take the page from very wide to narrower it alternates between wrapping the expression and not!

[FionaDyalog]

Not just I-beams, seeing this in other places too, for example, system functions.

[bear8642]

Not just an issue with narrowing the page - code element wraps when the page has space for the right hand contents menu too

[xpqz]

Well, what would you have it do instead? It's a responsive design, responding to changes in the viewport. If the width is too narrow for the content to fit, it must wrap.

[FionaDyalog]

It is wrapping before it needs to, and when the text could wrap instead. Let's discuss implementation and I'll describe how it's done in my Flare project and viable options for MKdocs (for example, moving the entire syntax section to a new line if there is insufficient space).