ratatui-v0.30.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-termion-v0.1.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-termwiz-v0.1.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-macros-v0.7.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-widgets-v0.3.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-crossterm-v0.1.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-core-v0.1.22026-06-19
a gift
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0302/>
⚠️ List of breaking changes can be found here.
Features
- 90639c1 (uncategorized) Add Termina backend by @joshka in #2561
> ## Summary
>
> - add the ratatui-termina backend crate using the published termina
> crate
> - expose the backend through the termina feature and Ratatui
> prelude/backend re-exports
> - add a small Termina event-loop example and wire the backend into CI,
> xtask, README generation, and docs
>
> Refs #1784
>
> ## Validation
>
> - cargo +nightly fmt
> - cargo check -p ratatui-termina --all-features --all-targets
> - cargo check -p ratatui --no-default-features --features termina
> - cargo check -p xtask
> - cargo check -p release-header
> - cargo xtask check-backend termina
> - cargo xtask test-backend termina
> - cargo xtask rdme --check
> - markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md
> .github/ISSUETEMPLATE/bugreport.md
>
> ---------
Bug Fixes
- fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #2584
> ## Summary
>
> - require custom shadow effects to preserve the auto traits expected by
> Block-backed widgets
> - document the CellEffect auto-trait contract
> - add a public widget regression test for the affected ratatui::widgets
> re-exports
>
> Fixes #2583
>
> ---------
- e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #2587
> When a wide cell from the previous buffer is replaced by a short/normal
> cell, the trailing cell does not get an update if its content does not
> change. But if the wide cell has a background (or other) style, the
> terminal did render the trailing cell with that style.
>
> Force trailing cells to update if background, underline, or modifiers
> are different than the wide cell. We can ignore foreground.
>
> Fixes #2585 (see that for the detailed visual reports)
- 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #2594
>
> Closes #2582.
>
> ## Problem
>
> When the content is shorter than the viewport, the thumb is large
> relative to the track. With the position at the end, part_lengths
> clamped thumbstart to tracklength - 1 while thumb_length was
> clamped independently to [1, tracklength], so thumbstart +
> thumblength could exceed tracklength.
>
> barsymbols lays out begin + trackstart + thumb + track_end + end
> and zips it against the cells of the area. When the thumb overruns the
> track, track_end saturates to 0 but the thumb still emits more cells
> than the track can hold, so the trailing end symbol is pushed past the
> end of the area. The last visible cell ends up being a thumb (█) where
> the end arrow (▼) should be.
>
> Concretely, for the issue's repro (VerticalRight, content_length =
> 9, position = 8, height 24): track is 22, thumb_length = 17,
> thumb_start = 6, and 6 + 17 = 23 > 22.
>
> This is a regression from v0.30.0, where thumb_length was derived as
> thumbend - thumbstart and therefore always fit within the track.
>
> ## Fix
>
> Clamp thumbstart to tracklength - thumb_length (instead of
> track_length - 1) so the thumb always fits within the track and the
> end symbol is preserved.
>
> ## Test
>
> Two regression tests, both fail on main and pass with the fix:
>
> - thumbstayswithintrackforlargethumbatend checks
> part_lengths directly with the issue's parameters — asserts
> thumbstart + thumblength <= track_length and that the parts sum to
> the track length.
> - renderscrollbarkeepsendsymbolforlarge_thumb renders the #2582
> case (both arrows, large thumb at the end) and asserts the end symbol is
> drawn rather than overwritten by a thumb cell.
>
> All existing scrollbar tests still pass.
Miscellaneous Tasks
- c75d778 (ci) Add cargo-udeps dependency check by @joshka in #2599
> Adds cargo xtask udeps and runs it from CI as a required job.
>
> This complements cargo-machete rather than replacing it. cargo-machete
> is a fast static source scan, which is why it missed the package-level
> unused deps fixed in #2598 when the same dependency names were still
> referenced by example crates. cargo-udeps compiles the workspace and
> checks rustc dep-info, so it can catch unused dependency declarations
> for the package being checked.
>
> To make the new job pass, this also removes the remaining true-positive
> unused dev-deps and records explicit cargo-udeps ignores for current
> false positives / intentional cases: ratatui-core critical-section,
> ratatui-crossterm's duplicate crossterm version feature shape, and
> ratatui-termwiz's doc-example-only ratatui dev-dependency.
>
> I searched existing issues and PRs for udeps / cargo-udeps / "cargo
> udeps". I did not find prior ratatui discussion about adopting
> cargo-udeps; the only hits were Dependabot PR bodies for
> taiki-e/install-action release notes mentioning cargo-udeps version
> updates, for example #1971, #2095, #2194, and #2522.
>
> Validation:- cargo xtask udeps
> - cargo xtask format --check
>
> ---------
- 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #2598
> Audit removes these dependencies that are not used:
>
> ratatui/Cargo.toml — Removed from [dev-dependencies]:
> - futures
> - rand_chacha
> - tokio
> - tracing
> - tracing-appender
> - tracing-subscriber
>
> ratatui-core/Cargo.toml — Moved from [dependencies] →
> [dev-dependencies]:
> - indoc
>
> ---------
Continuous Integration
- 36854ef (uncategorized) Add auto-merge required gate by @joshka in #2596
> ## Summary
>
> This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
> happy with the change but CI is still running.
>
> The workflow change adds a single aggregate required job to the main
> CI workflow. The repository now has auto-merge
> enabled
> and an ensure checks pass
> ruleset
> that requires that required status context on main.
>
> ## Why
>
> Without a required status context, GitHub's auto-merge button is not
> useful for the maintainer flow we want. The goal is to let a mainta
ratatui-v0.30.12026-06-05
> "Rats, we're rats; we're the rats." – Rat Movie
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0301/>
⚠️ List of breaking changes can be found here.
Features
- 74d6a84 (block) Support shadows by orhun in #2481
> Introduce Block::shadow(...) with a new Shadow type that supports:
>
> - presets: overlay, block, lightshade, mediumshade,
> dark_shade
> - custom symbols via Shadow::symbol(...)
> - custom effects via Shadow::custom(...)
>
> ``rust
> use ratatui::layout::Offset;
> use ratatui::style::Stylize;
> use ratatui::widgets::{Block, Shadow};
>
> let popup = Block::bordered().title("Popup").shadow(
> Shadow::dark_shade()
> .black()
> .on_white()
> .offset(Offset::new(2, 1)),
> );
> `
>
> Results in:
>
> `
> ┌Popup─────┐
> │content │▒
> └──────────┘▒
> ▒▒▒▒▒▒▒▒▒▒▒
> `
>
> shadow
>
> fixes #1892
>
> ---------
- 4d30420 (buffer) Add CellDiffOption::AlwaysUpdate to force cell updates by sxyazi in #2480
> When this option is used, the cells are updated even when content is identical.
>
> Follow-up for https://github.com/ratatui/ratatui/pull/1605
>
> Trying to resolve https://github.com/ratatui/ratatui/issues/1116
- 39c32c6 (buffer) Add cell diff options by benjajaja in #1605
>
> Problem:Escape sequences always cause a cell to count as "multiwidth",
> even when it doesn't render wider than one cell, or not as wide as the
> escape sequence would be computed as.
>
> Solution:Convert skip:bool to enum. Add enum option ForceWidth to
> force a cell width for diffing.
>
> When using the option, this also fixes some bug where diffing is not
> idempotent and causes a diff operation for (symbol.len() - 1) times.
>
> There are three new specific test cases:
>
> 1. Rendering hyperlinks by squeezing the escape sequence into the first
> cell and forcing the width to the unicode width of the text part.
> This is much easier to implement for a Link widget, as it would only
> need to get the unicode-width once and not iterate over graphemes
> like Spans must do.
> 2. Rendering hyperlinks by squeezing the opening sequence into the first
> cell with the first grapheme and forcing the width to that of the
> first grapheme. Then rendering each grapheme as usual. Then squeezing
> the closing sequence into the last cell with the last grapheme and
> forcing the width to that of the last grapheme.
> This is harder to implement for a Link widget, as it would have to
> iterate over graphemes with their width like Spans do.
> 3. Kitty image sequence with utf-8 placeholders, similar to 2 but with
> known constant grapheme widths.
>
> ### Link widget that leverages this
>
> https://github.com/benjajaja/tui-link
>
>
>
> It would be cooler if we could just add something like .link(url) to
> Spans, because it would much simpler to insert some link and leverage
> all the Line/Text/Paragraph wrapping and whatnot. With a custom widget
> you need to take care of the Area where you'd want to render it, so
> it's not that clean. But we could iterate on this later, if even
> possible.
- 6faaddb (core) Implement from slice for line and text by NoOPeEKS in #2371
> This PR adds the following implementations of the From trait for Line
> and Text structs:
>
> - Implements From<&[T]> where T is Into\<Span> for Line, allowing using
> of slices to construct Lines.
> - Implements From<&[T]> where T is Into\<Line> for Text, allowing using
> of slices of various types to construct Texts.
>
> closes #2279
- 5fc6ab8 (core) Support layout-cache in no_std environments by junkdog in #2399
> this enables "layout-cache" for no_std builds; it's meant for embedded
> environments, where the layout engine otherwise consumes all CPU,
> capping the framerate at around ~10fps. the same app can refresh 300-500
> times per second with layout cache enabled.
>
> i had to add layout-cache = ["dep:critical-section"] to all builds -
> it's pretty tiny and shouldn't leave a trace in std-builds. the
> alternative is to add an extra layer of features for layout-cache with
> std and no_std, but it pollutes the feature space.
>
> ---------
- ee4b7a9 (crossterm) Add the missing hidden modifier by sxyazi in #2413
> Fixes https://github.com/sxyazi/yazi/issues/3724, see
> https://github.com/sxyazi/yazi/issues/3724#issuecomment-3970129744 for a
> reproducer.
>
> This PR adds the missing Modifier::HIDDEN style and introduces a
> queuemodifierdiff to test ModifierDiff::queue().
>
> It also fixes a bug where CrosstermAttribute::Bold and
> CrosstermAttribute::Dim would be emitted twice when resetting
> intensity. For example:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold])]
> `
>
> would become:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold, CrosstermAttribute::Bold])]
> `
>
> ---------
- 9d9239a (examples) Add volatility-surface 3D visualization by floor-licker in #2322
> A design demonstration of a 3D volatility surface rendering using
> Braille canvas with interactive rotation and zoom controls. I built this
> for myself for an app I'm currently building but just wanted to share it
> with the community as well to inspire more 3D perspective terminal
> widgets in the future.
>
> ## Final Demo
>
> volatility-surface
>
> ## Description
>
> Adds a new example demonstrating 3D visualization techniques in the
> terminal. There aren't many examples showing how to represent 3D objects
> in 2D terminal space so my goal is just to demonstrate more advanced
> Canvas and Braille rendering techniques for 3D graphics. The example
> visualizes an implied volatility surface which is a common financial
> visualization using interactive rotation and zoom controls. You can run
> the interactive demo for yourself with cargo run -p volatility-surface`
>
> https://github.com/user-attachments/assets/aa32a864-54a8-4c67-a3c9-432dd29373fd
>
> <img width="659" height="432" alt="image"
>
> src="https://github.com/user-attachments/assets/68698cb0-c5d5-4b41-a3c3-65ec8fff12f5"
> />
>
> ## Technical Highlights
>
> - Demonstrates how to implement perspective projection i
ratatui-termion-v0.1.12026-06-05
> "Rats, we're rats; we're the rats." – Rat Movie
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0301/>
⚠️ List of breaking changes can be found here.
Features
- 74d6a84 (block) Support shadows by orhun in #2481
> Introduce Block::shadow(...) with a new Shadow type that supports:
>
> - presets: overlay, block, lightshade, mediumshade,
> dark_shade
> - custom symbols via Shadow::symbol(...)
> - custom effects via Shadow::custom(...)
>
> ``rust
> use ratatui::layout::Offset;
> use ratatui::style::Stylize;
> use ratatui::widgets::{Block, Shadow};
>
> let popup = Block::bordered().title("Popup").shadow(
> Shadow::dark_shade()
> .black()
> .on_white()
> .offset(Offset::new(2, 1)),
> );
> `
>
> Results in:
>
> `
> ┌Popup─────┐
> │content │▒
> └──────────┘▒
> ▒▒▒▒▒▒▒▒▒▒▒
> `
>
> shadow
>
> fixes #1892
>
> ---------
- 4d30420 (buffer) Add CellDiffOption::AlwaysUpdate to force cell updates by sxyazi in #2480
> When this option is used, the cells are updated even when content is identical.
>
> Follow-up for https://github.com/ratatui/ratatui/pull/1605
>
> Trying to resolve https://github.com/ratatui/ratatui/issues/1116
- 39c32c6 (buffer) Add cell diff options by benjajaja in #1605
>
> Problem:Escape sequences always cause a cell to count as "multiwidth",
> even when it doesn't render wider than one cell, or not as wide as the
> escape sequence would be computed as.
>
> Solution:Convert skip:bool to enum. Add enum option ForceWidth to
> force a cell width for diffing.
>
> When using the option, this also fixes some bug where diffing is not
> idempotent and causes a diff operation for (symbol.len() - 1) times.
>
> There are three new specific test cases:
>
> 1. Rendering hyperlinks by squeezing the escape sequence into the first
> cell and forcing the width to the unicode width of the text part.
> This is much easier to implement for a Link widget, as it would only
> need to get the unicode-width once and not iterate over graphemes
> like Spans must do.
> 2. Rendering hyperlinks by squeezing the opening sequence into the first
> cell with the first grapheme and forcing the width to that of the
> first grapheme. Then rendering each grapheme as usual. Then squeezing
> the closing sequence into the last cell with the last grapheme and
> forcing the width to that of the last grapheme.
> This is harder to implement for a Link widget, as it would have to
> iterate over graphemes with their width like Spans do.
> 3. Kitty image sequence with utf-8 placeholders, similar to 2 but with
> known constant grapheme widths.
>
> ### Link widget that leverages this
>
> https://github.com/benjajaja/tui-link
>
>
>
> It would be cooler if we could just add something like .link(url) to
> Spans, because it would much simpler to insert some link and leverage
> all the Line/Text/Paragraph wrapping and whatnot. With a custom widget
> you need to take care of the Area where you'd want to render it, so
> it's not that clean. But we could iterate on this later, if even
> possible.
- 6faaddb (core) Implement from slice for line and text by NoOPeEKS in #2371
> This PR adds the following implementations of the From trait for Line
> and Text structs:
>
> - Implements From<&[T]> where T is Into\<Span> for Line, allowing using
> of slices to construct Lines.
> - Implements From<&[T]> where T is Into\<Line> for Text, allowing using
> of slices of various types to construct Texts.
>
> closes #2279
- 5fc6ab8 (core) Support layout-cache in no_std environments by junkdog in #2399
> this enables "layout-cache" for no_std builds; it's meant for embedded
> environments, where the layout engine otherwise consumes all CPU,
> capping the framerate at around ~10fps. the same app can refresh 300-500
> times per second with layout cache enabled.
>
> i had to add layout-cache = ["dep:critical-section"] to all builds -
> it's pretty tiny and shouldn't leave a trace in std-builds. the
> alternative is to add an extra layer of features for layout-cache with
> std and no_std, but it pollutes the feature space.
>
> ---------
- ee4b7a9 (crossterm) Add the missing hidden modifier by sxyazi in #2413
> Fixes https://github.com/sxyazi/yazi/issues/3724, see
> https://github.com/sxyazi/yazi/issues/3724#issuecomment-3970129744 for a
> reproducer.
>
> This PR adds the missing Modifier::HIDDEN style and introduces a
> queuemodifierdiff to test ModifierDiff::queue().
>
> It also fixes a bug where CrosstermAttribute::Bold and
> CrosstermAttribute::Dim would be emitted twice when resetting
> intensity. For example:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold])]
> `
>
> would become:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold, CrosstermAttribute::Bold])]
> `
>
> ---------
- 9d9239a (examples) Add volatility-surface 3D visualization by floor-licker in #2322
> A design demonstration of a 3D volatility surface rendering using
> Braille canvas with interactive rotation and zoom controls. I built this
> for myself for an app I'm currently building but just wanted to share it
> with the community as well to inspire more 3D perspective terminal
> widgets in the future.
>
> ## Final Demo
>
> volatility-surface
>
> ## Description
>
> Adds a new example demonstrating 3D visualization techniques in the
> terminal. There aren't many examples showing how to represent 3D objects
> in 2D terminal space so my goal is just to demonstrate more advanced
> Canvas and Braille rendering techniques for 3D graphics. The example
> visualizes an implied volatility surface which is a common financial
> visualization using interactive rotation and zoom controls. You can run
> the interactive demo for yourself with cargo run -p volatility-surface`
>
> https://github.com/user-attachments/assets/aa32a864-54a8-4c67-a3c9-432dd29373fd
>
> <img width="659" height="432" alt="image"
>
> src="https://github.com/user-attachments/assets/68698cb0-c5d5-4b41-a3c3-65ec8fff12f5"
> />
>
> ## Technical Highlights
>
> - Demonstrates how to implement perspective projection i
ratatui-termwiz-v0.1.12026-06-05
> "Rats, we're rats; we're the rats." – Rat Movie
We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨🍳🐀
✨ Release highlights: <https://ratatui.rs/highlights/v0301/>
⚠️ List of breaking changes can be found here.
Features
- 74d6a84 (block) Support shadows by orhun in #2481
> Introduce Block::shadow(...) with a new Shadow type that supports:
>
> - presets: overlay, block, lightshade, mediumshade,
> dark_shade
> - custom symbols via Shadow::symbol(...)
> - custom effects via Shadow::custom(...)
>
> ``rust
> use ratatui::layout::Offset;
> use ratatui::style::Stylize;
> use ratatui::widgets::{Block, Shadow};
>
> let popup = Block::bordered().title("Popup").shadow(
> Shadow::dark_shade()
> .black()
> .on_white()
> .offset(Offset::new(2, 1)),
> );
> `
>
> Results in:
>
> `
> ┌Popup─────┐
> │content │▒
> └──────────┘▒
> ▒▒▒▒▒▒▒▒▒▒▒
> `
>
> shadow
>
> fixes #1892
>
> ---------
- 4d30420 (buffer) Add CellDiffOption::AlwaysUpdate to force cell updates by sxyazi in #2480
> When this option is used, the cells are updated even when content is identical.
>
> Follow-up for https://github.com/ratatui/ratatui/pull/1605
>
> Trying to resolve https://github.com/ratatui/ratatui/issues/1116
- 39c32c6 (buffer) Add cell diff options by benjajaja in #1605
>
> Problem:Escape sequences always cause a cell to count as "multiwidth",
> even when it doesn't render wider than one cell, or not as wide as the
> escape sequence would be computed as.
>
> Solution:Convert skip:bool to enum. Add enum option ForceWidth to
> force a cell width for diffing.
>
> When using the option, this also fixes some bug where diffing is not
> idempotent and causes a diff operation for (symbol.len() - 1) times.
>
> There are three new specific test cases:
>
> 1. Rendering hyperlinks by squeezing the escape sequence into the first
> cell and forcing the width to the unicode width of the text part.
> This is much easier to implement for a Link widget, as it would only
> need to get the unicode-width once and not iterate over graphemes
> like Spans must do.
> 2. Rendering hyperlinks by squeezing the opening sequence into the first
> cell with the first grapheme and forcing the width to that of the
> first grapheme. Then rendering each grapheme as usual. Then squeezing
> the closing sequence into the last cell with the last grapheme and
> forcing the width to that of the last grapheme.
> This is harder to implement for a Link widget, as it would have to
> iterate over graphemes with their width like Spans do.
> 3. Kitty image sequence with utf-8 placeholders, similar to 2 but with
> known constant grapheme widths.
>
> ### Link widget that leverages this
>
> https://github.com/benjajaja/tui-link
>
>
>
> It would be cooler if we could just add something like .link(url) to
> Spans, because it would much simpler to insert some link and leverage
> all the Line/Text/Paragraph wrapping and whatnot. With a custom widget
> you need to take care of the Area where you'd want to render it, so
> it's not that clean. But we could iterate on this later, if even
> possible.
- 6faaddb (core) Implement from slice for line and text by NoOPeEKS in #2371
> This PR adds the following implementations of the From trait for Line
> and Text structs:
>
> - Implements From<&[T]> where T is Into\<Span> for Line, allowing using
> of slices to construct Lines.
> - Implements From<&[T]> where T is Into\<Line> for Text, allowing using
> of slices of various types to construct Texts.
>
> closes #2279
- 5fc6ab8 (core) Support layout-cache in no_std environments by junkdog in #2399
> this enables "layout-cache" for no_std builds; it's meant for embedded
> environments, where the layout engine otherwise consumes all CPU,
> capping the framerate at around ~10fps. the same app can refresh 300-500
> times per second with layout cache enabled.
>
> i had to add layout-cache = ["dep:critical-section"] to all builds -
> it's pretty tiny and shouldn't leave a trace in std-builds. the
> alternative is to add an extra layer of features for layout-cache with
> std and no_std, but it pollutes the feature space.
>
> ---------
- ee4b7a9 (crossterm) Add the missing hidden modifier by sxyazi in #2413
> Fixes https://github.com/sxyazi/yazi/issues/3724, see
> https://github.com/sxyazi/yazi/issues/3724#issuecomment-3970129744 for a
> reproducer.
>
> This PR adds the missing Modifier::HIDDEN style and introduces a
> queuemodifierdiff to test ModifierDiff::queue().
>
> It also fixes a bug where CrosstermAttribute::Bold and
> CrosstermAttribute::Dim would be emitted twice when resetting
> intensity. For example:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold])]
> `
>
> would become:
>
> `rust
> #[case(Modifier::DIM, Modifier::BOLD, &[CrosstermAttribute::NormalIntensity, CrosstermAttribute::Bold, CrosstermAttribute::Bold])]
> `
>
> ---------
- 9d9239a (examples) Add volatility-surface 3D visualization by floor-licker in #2322
> A design demonstration of a 3D volatility surface rendering using
> Braille canvas with interactive rotation and zoom controls. I built this
> for myself for an app I'm currently building but just wanted to share it
> with the community as well to inspire more 3D perspective terminal
> widgets in the future.
>
> ## Final Demo
>
> volatility-surface
>
> ## Description
>
> Adds a new example demonstrating 3D visualization techniques in the
> terminal. There aren't many examples showing how to represent 3D objects
> in 2D terminal space so my goal is just to demonstrate more advanced
> Canvas and Braille rendering techniques for 3D graphics. The example
> visualizes an implied volatility surface which is a common financial
> visualization using interactive rotation and zoom controls. You can run
> the interactive demo for yourself with cargo run -p volatility-surface`
>
> https://github.com/user-attachments/assets/aa32a864-54a8-4c67-a3c9-432dd29373fd
>
> <img width="659" height="432" alt="image"
>
> src="https://github.com/user-attachments/assets/68698cb0-c5d5-4b41-a3c3-65ec8fff12f5"
> />
>
> ## Technical Highlights
>
> - Demonstrates how to implement perspective projection i