Sometimes invisible since start

[ghost]

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

River

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

Sometimes the window becomes completely invisible (except WM deco) since start and stays like that.

To Reproduce

Launch Wezterm from a River bind with my River and Wezterm config files.

Configuration

--- Meta ---------------------
-- API
local wt = require 'wezterm'
-- Return options as a type able to log and make errors
local o = wt.config_builder()

--- Options ------------------
-- UI
o.color_scheme = 'Tokyo Night'
o.colors = {
	tab_bar = {
		active_tab = { bg_color = '#1A1B26', fg_color = '#C0CAF5' },
		inactive_tab = { bg_color = 'black', fg_color = '#C0CAF5' },
		new_tab = { bg_color = 'black', fg_color = '#C0CAF5' },
		background = 'black'
	}
}
o.font = wt.font_with_fallback { 'Noto Sans Mono', 'Nerd Fonts Symbols', 'Noto Color Emoji' }
o.window_padding = { left = 0, right = 0, top = 0, bottom = 0 }
o.show_new_tab_button_in_tab_bar = false
o.hide_tab_bar_if_only_one_tab = true
o.use_fancy_tab_bar = false
o.font_size = 12

-- Behavior
-- o.default_prog = { 'powershell', '-NoLogo' }
o.window_close_confirmation = 'NeverPrompt'
o.use_dead_keys = false

-- Binds
o.keys = {
	{ key = 'q', mods = 'CTRL', action = wt.action.CloseCurrentTab { confirm = false } },
	{ key = 'q', mods = 'CMD', action = wt.action.CloseCurrentTab { confirm = false } }
}


return o

Expected Behavior

Window isn't invisible.

Logs

No response

Anything else?

No response

[VoltaireNoir]

Facing the same issue on river with attach-mode set to bottom. This happens when I spawn more than 3 windows on the same tag, but works fine if I have more than 3 in total distributed across different tags. This is unique to wezterm because other programs work fine when I do the same with them (firefox, for example).

It's important to note that this doesn't happen when the attach-mode is set to top (default). In that mode, the new window will take up the master stack. I suspect this bug is related to the window being resized to a smaller size when it is created, because that is what happens with bottom attach mode, every new window gets smaller and smaller.