Consider separating TextEdit keyboard interactivity vs mouse interactivity

[crumblingstatue]

I have a music player with a terminal output panel using TextEdit. The music player also allows interacting with the terminal applications (it forwards egui key events to their PTY).

The TextEdit itself is immutable (uses the &mut &str trick), however it still eats up keyboard events if focused, despite not being editable.

I have this hack to make it not do that if nothing is selected.

                // Weird hack to make PTY interaction work even if the TextEdit was clicked.
                // Normally, the `TextEdit` is interested in keyboard events even in the
                // "immutable" mode, which is not what we want.
                // But unconditionally surrendering focus also deselects, so we first check if
                // nothing is being selected.
                let out = TextEdit::multiline(&mut out.as_str())
                    .desired_width(620.0)
                    .font(TextStyle::Monospace)
                    .show(ui);
                if out
                    .cursor_range
                    .is_none_or(|range| range.primary == range.secondary)
                {
                    out.response.surrender_focus();
                }

It would be nice if there was direct support for "not interested in keyboard, but still selectable".
TextEdit::interactive conflates the two.