Skip to content

(macOS) "Ghost content" with non-native fullscreen #6086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
qwerasd205 opened this issue Mar 5, 2025 · 4 comments
Open

(macOS) "Ghost content" with non-native fullscreen #6086

qwerasd205 opened this issue Mar 5, 2025 · 4 comments
Labels
gui GUI or app issue regardless of platform (i.e. Swift, GTK) os/macos

Comments

@qwerasd205
Copy link
Member

qwerasd205 commented Mar 5, 2025

Running on macOS Sequoia, with the following config:

background-opacity = 0
macos-non-native-fullscreen = visible-menu
fullscreen = true
window-save-state = always

If I have some information displayed on screen, switch to another space, come back, then clear my screen I get some ghost display from the previous data. I need to exit full screen mode to remove the ghost writing or switch space again. It happens in every split. See attached
Screenshot 2025-02-11 at 14 34 21

Originally posted by @kTag in #5674

Note

Looking closely it seems the compositor is applying some sort of drop shadow effect to the contents with non-native-fullscreen set like that, and it's only updating when switching spaces.

Idk off the top of my head what the correct solution is here - probably some way to signal to the compositor that the contents have changed in a way that the shadow needs to be recomputed - but it's well scoped enough to be turned in to an issue at this point.

@qwerasd205 qwerasd205 added os/macos gui GUI or app issue regardless of platform (i.e. Swift, GTK) labels Mar 5, 2025
@utensil
Copy link

utensil commented Apr 25, 2025

Setting macos-window-shadow = false will make this issue go away completely, per my test. See https://ghostty.org/docs/config/reference#macos-window-shadow .

@qwerasd205
Copy link
Member Author

That's a useful hint- we should disable the shadow while non native fullscreen is active, which should fix this.

@00-kat
Copy link
Contributor

00-kat commented Apr 26, 2025

I know basically nothing about this topic, but somebody else had this exact same issue with the exact same resolution at #7199, except they were not using the non-native full-screen; this issue may perhaps not be limited to the non-native full-screen.

@mitchellh
Copy link
Contributor

Hm. Maybe related to window shadows with any kind of transparency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gui GUI or app issue regardless of platform (i.e. Swift, GTK) os/macos
Projects
None yet
Development

No branches or pull requests

4 participants