Proposal: updating text controls to properly handle large files
<!-- This is a template for new feature or API proposals. For example you can use this to propose a new API on an existing type, or an idea for a new UI control. It's fine if you don't have all the details: you can start with the Summary and Rationale. This link describes the WinUI feature/API proposal process: https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/feature_proposal_process.md --> # Proposal: updating text controls to properly handle large files <!-- Add a title for your feature or API proposal. Please be short and descriptive --> Creating this issue as suggested by @anawishnoff [on Twitter](https://twitter.com/ana_wishnoff/status/1217147791010496513). This proposal links back to a similar one on the UWP Community Toolkit about a [virtualized RichEditBox control](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/2858). ## Summary <!-- Include 1-2 sentences summarizing your feature or API proposal --> One common complaints about the native text controls on UWP (namely, `TextBlock`, `TextBox`, `RichTextBlock`, `RichEditBox`) is that they are not able to properly handle large files. Trying to load a 1MB text file into any of those controls will cause apps to either become unsustainably slow, or just crash. So far developers have either had to limit functionality in their apps to avoid hitting this issue, implement solutions like using multiple `TextBlock` controls in a virtualized items panel (which has its own set of downsides), or re
Posted by Sergio0694 on Jan 14, 2020, 6:28 PM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Proposal: updating text controls to properly handle large files
<!-- This is a template for new feature or API proposals. For example you can use this to propose a new API on an existing type, or an idea for a new UI control. It's fine if you don't have all the details: you can start with the Summary and Rationale. This link describes the WinUI feature/API proposal process: https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/feature_proposal_process.md --> # Proposal: updating text controls to properly handle large files <!-- Add a title for your feature or API proposal. Please be short and descriptive --> Creating this issue as suggested by @anawishnoff [on Twitter](https://twitter.com/ana_wishnoff/status/1217147791010496513). This proposal links back to a similar one on the UWP Community Toolkit about a [virtualized RichEditBox control](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/2858). ## Summary <!-- Include 1-2 sentences summarizing your feature or API proposal --> One common complaints about the native text controls on UWP (namely, `TextBlock`, `TextBox`, `RichTextBlock`, `RichEditBox`) is that they are not able to properly handle large files. Trying to load a 1MB text file into any of those controls will cause apps to either become unsustainably slow, or just crash. So far developers have either had to limit functionality in their apps to avoid hitting this issue, implement solutions like using multiple `TextBlock` controls in a virtualized items panel (which has its own set of downsides), or re
Comments (0)
No comments yet. Start the discussion.