3 ms·
I don't know where's the improvements, give it has all the limitations, now scaled to rich text. That's not the direction that this component should get. It nee
by krzyzanowskim 5mo ago
I don't know where's the improvements, give it has all the limitations, now scaled to rich text. That's not the direction that this component should get. It need radical new API that is not much compatible with SwiftUI API
- CharlesW 5mo agoYou must know far more about this than me, but as of iOS 26, `TextEditor` evolved into a true rich text editor (`AttributedString` binding, `AttributedTextSelection` rich text selection, custom/app-specific text attributes, etc). https://developer.apple.com/videos/play/wwdc2025/280/ https://developer.apple.com/videos/play/wwdc2025/280/ Do you really think people should use web views instead of, say, STTextView?
- krzyzanowskim 5mo agoI think people should use anything but SwiftUI.TextEditor is my current stance