Automatically disabling background opacity with Mac fullscreen doesn't seem to work

[maciejzj]

Hi, I may be missing something but from what I understand from this discussion: #2840, as well as from this fragment of documentation: https://ghostty.org/docs/config/reference#background-opacity, particularly this paragraph:

On macOS, background opacity is disabled when the terminal enters native fullscreen. This is because the background becomes gray and it can cause widgets to show through which isn't generally desirable.

when I enter Mac fullscreen the background opacity should turn off. However, on my system it seems to still be on which causes the undesired effect of widgets showing through.

Here is how it looks like:

compressed_ghostty.mov

Doesn't the actual behaviour go against the documentation? Am I missing something? Is this a bug?

Here's my config:

# Text settings
font-family = Liga SFMono Nerd Font
font-feature = -calt
adjust-cell-width = -5%

# Makes ghostty to fallback to the default block cursor
shell-integration-features = no-cursor

# UI settings
window-padding-x = 5
window-padding-y = 3
window-width = 86
window-height = 26

theme = catppuccin-mocha
background-opacity = 0.8
# background-opacity = 0.96
background-blur-radius = 50

# System behaviour
window-inherit-working-directory = false

# Keyboard settings
macos-option-as-alt = left
macos-non-native-fullscreen = false

Ghostty version:

(the problem also persists with the stable release from the website/brew as well)

[sghng]

I have same issue! #5986 also mentioned this

[nyngwang]

I can confirm this. (Those in the background are Ubersicht apps.)

[nyngwang]

@maciejzj After some testing, settingmacos-titlebar-style = hidden seems to make it work as expected. (but then you might not like hidden tho, since it's a bit hard to drag by mouse. just trying to help)

[mitchellh]

We haven't heard further reports since Ghostty 1.2. This issue is very old and we've completely rewritten the fullscreen logic since. If this issue is still happening in specific cases, please open a new discussion.