Hi @everuribe,

This is a known issue of MarkdownUI. The current implementation combines multiple Text and Image views into containing layout views, which makes text selection work only at a paragraph level. I don't have a solution at the moment, but I am trying different things to make text selection work.

Thanks for the context! I guess it relies on newlines to be able to switch to a different markdown type and therefore view but maybe we can detect if it's just a continuation of the same markdown type and keep it in the same Text view? I assume this is already happening for code blocks.

It's a bit more complicated than that. It doesn't rely on newlines, as spacing is configurable per block. On top of that, styling adds yet another layer of indirection. Regarding code blocks, those are rendered in a single view, so it works as you would expect.

As a workaround, you could add a gesture to the Markdown view that displays a context menu with an item to copy the contents.

I found it's not working on Mac Catalyst

1 for this one - I'll add that being able to highlight individual words, as is typically seen when using Edit Menus would be ideal, however being able to copy an entire view, rather than one paragraph at a time would be a decent fallback.

I know this is not (shockingly) possible with a SwiftUI Text view, and I'm not particularly optimistic about finding a way to implement it, but wanted to add this feedback

1 on this issue. Would love to be able to do this at some point.

I was just checking in/wanted to voice my support on this as well, since I'm looking to add a feature that would let users highlight specific text in a Reader Mode I'm implementing. Thanks for the great library!

In case it helps prioritize this, we are switching off this library on our next project specifically because of this issue. The number one request from users is the ability to simply copy the formatted text out like any other app would.

Same - I ended up rolling my own UIViewRepresentable based on UITextView to support this feature, but would move back to this component in a heartbeat if this were to be prioritized

I'm on the same boat. Is there a way to fund this?

Hi all,

As mentioned in a previous comment, fixing this issue is challenging. The key is accessing and controlling the text layout(s) in a view hierarchy.

I am working on a replacement for SwiftUI Text view based on Canvas and Core Text, and the results look promising. However, there is still a lot of work to do, and I can't provide an ETA.

Thank you for being so patient!

Amazing, thanks @gonzalezreal for the update, much appreciated!