TextInput

_release-content/migration-guides/text_input.md

@@ -0,0 +1,9 @@
+---
+title: "EditableText readonly and display-only modes"
+pull_requests: []
+---
+
+Previously, the `EditableText` component functioned as both a holder for the state of a editable
+text, and as a standalone widget, with observers and keyboard mappings. These two functions have
+been separated: to make a complete, working text input widget, you will now need to insert
+both an `EditableText` and a `TextInput` component.

_release-content/release-notes/text_input.md

@@ -0,0 +1,15 @@
+---
+title: "TextInput"
+authors: ["@viridia"]
+pull_requests: []
+---
+
+The `EditableText` component has been split into two components, which are now `EditableText`
+and `TextInput`. The `EditableText` component, which lives in the `bevy::text` crate, holds the
+state of a text input field, but no longer has any built-in observers - that is, it does not
+behave like a widget (headless or otherwise), but merely a holder of state.
+
+All of the widget-like behaviors (responding to keystrokes) have been moved to a new `TextInput`
+component which lives in the `bevy::ui_widgets` crate. Not only is the arrangement more consistent
+with the other widgets, but in addition this new component also has properties which are only
+interesting to widgets, like a "read-only" option.