mirror of
https://github.com/wez/wezterm.git
synced 2024-12-25 06:12:16 +03:00
808d7df8d4
In https://github.com/wez/wezterm/pull/1779#issuecomment-1082058134 we discuss a weird case where the tab bar height is computed as 0 and then gets stuck at 0. What's happening is that the initial `TabBarState::default()` value has no items yet, and `build_fancy_tab` generates an area that occupies 0 pixels. This computed element is cached, and then the height from that is cached. When `invalidate_fancy_tab` is called, it didn't invalidate the cached height and the resultant metrics were wonky. One possible fix for this was to also invalidate the cached height, but since that height is already stored in the built fancy tab, we can remove that derived-cached value in favor of just passing down the value. refs: https://github.com/wez/wezterm/pull/1779 |
||
---|---|---|
.. | ||
src | ||
build.rs | ||
Cargo.toml |