Text rendering performance is embarrassingly bad about microsoft-ui-xaml HOT 4 OPEN

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• RichEditBox performance issues (#9498), similarity score: 0.74

Closed similar issues:

• TextBox performance issue (load times ~5x slower compared to WPF) (#3336), similarity score: 0.75
• Severe performance issues in WinUI 3 (#6031), similarity score: 0.73
• Scrolling is very slow when binding the TextProperty in WinUI TextBlock (#5191), similarity score: 0.72
• Text not rendered in RichEditBox when large number of lines present (#1989), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

from microsoft-ui-xaml.

TextBlock does not use virtualization, neither does RichTextBlock, so all that text will be rendered even if not in view. I don't think the text boxes have virtualization either (see #1842), so I suppose your best bet for now would be using a ListView - not ideal, but it should work well enough.

from microsoft-ui-xaml.

TextBlock does not use virtualization, neither does RichTextBlock, so all that text will be rendered even if not in view. I don't think the text boxes have virtualization either (see #1842), so I suppose your best bet for now would be using a ListView - not ideal, but it should work well enough.

Using a ListView you have to do tons more work to handle text wrapping. Lacking of virtualization definitely needs to be addressed

from microsoft-ui-xaml.

Using a ListView you have to do tons more work to handle text wrapping

As a workaround, if you have the text line by line, it should be possible to use a DataTemplate with a horizontally stretched TextBlock, and set its text wrapping mode to Wrap. But that wouldn't work if you have a bunch of text on a single line, and thinking about it a bit more, selection with that would likely be a pain, needing to be handled manually.

Lacking of virtualization definitely needs to be addressed

Agreed, this would be particularly good for edit boxes. But seeing the other issue's status, I doubt it's particularly high priority.

from microsoft-ui-xaml.