v4.0.5

What's Changed

• Add license metadata to pyproject.toml by @cycledriver in #40

New Contributors

• @cycledriver made their first contribution in #40

Full Changelog: v4.0.4...v4.0.5

4.0.4

Input.Changed events are now prevented on applying completions internally, so that users don't have to do it if they override apply_completion.

v4.0.2

Changed

• Improve how we align the dropdown with the cursor (padding/align rules on parent containers will not affect dropdown position).

Fixed

• Fix missing event.stop() on up key press when dropdown open.
• Ensure dropdown is correctly constrained within content region.

Full Changelog: v4.0.1...v4.0.2

v4.0.1 - Rewrite

Rewrites textual-autocomplete to support Textual 2.0+.

Don't ask me about version 3.

Here, have some clips:

Colors!

Paths!

textual-autocomplete-4-path-completion__76pct_smaller.mp4

Another Video!

Screen.Recording.2025-03-18.at.21.28.42.mov

New Contributors

• @davep made their first contribution in #35

Full Changelog: v2.1.0b0...v4.0.1

Support for Textual 0.16.0+

This release adds support for newer versions of Textual.

Note that on Textual 0.16.0, there may be small visual glitches when tabbing between Inputs which use autocompletes. This bug is fixed inside Textual itself and the fix will be part of Textual 0.17.0, which should drop this week.

What's Changed

• Textual v0.14.0 compat by @UmBsublime in #12
• feat: only react to key events (and stop them) when dropdown is displayed by @jtyers in #9
• feat: only show dropdown if input widget currently has focus by @jtyers in #8

New Contributors

• @UmBsublime made their first contribution in #12
• @jtyers made their first contribution in #9

Full Changelog: v2.0.0b0...v2.1.0b0

v2.0.0b0 - Custom completion callbacks, small API changes

• Support custom completion logic: when you select an item from a dropdown, you are now able to pass a callback function giving fine-grained control over the new state of the input.
• Encapsulated cursor_position and value into a new InputState object.

v1.2.0b0 - Option to retain focus on Input after using Tab key to complete

Previously, when you press the Tab key to select a completion, the Input would be filled with the chosen value and focus would go to the next widget in Textual's focus chain.

Now, this behaviour is disabled by default. Pressing the Tab key to select an item in the dropdown will still fill the item, but it won't move focus. The input will behave as normal after the completion - so you can press Tab again to switch focus.

The previous functionality is still available via a new tab_moves_focus boolean switch available on the AutoComplete class.

v1.1.0b0 - Support for Textual 0.11.0+

There were some breaking API changes in the latest version of Textual. This release makes textual-autocomplete compatible with them.

Thanks to a Textual bugfix, the content of your dropdown can now be updated whenever the cursor position changes inside the dropdown.

v1.0.1b0 - Support for Textual 0.10.0+

This release adds support for newer Textual versions.

v1.0.0b0

Initial beta release of textual-autocomplete.