| Age | Commit message (Collapse) | Author |
|---|
|
Co-authored-by: tadeokondrak <me@tadeo.ca>
|
|
Check if the app that requested a token has provided a valid input
serial and a focused surface. Downgrade activation request to urgency
otherwise.
This is mostly in line with what other Wayland compositors decided to
do, and offers a better security than the original logic.
|
|
This is a more suitable place to track the requesting seat, since we are
able to respond appropriately to destroy notifications.
|
|
|
|
The header is not installed by wlroots when the DRM backend is
disabled. We don't need it here, so don't include it.
Closes: https://github.com/swaywm/sway/issues/7943
|
|
It's not used and causes a crash when a view is destroyed.
|
|
We tried to synchronize layer shell popups with the parent layer shell
on commits, but this is subtly wrong because we would only update
the position for one layer shell that was committed, but not any other
layer that might be affected. By moving handling to the scene descriptor
we can iterate all popups and ensure they are synchronized.
|
|
|
|
|
|
References: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4543
|
|
7e69a7076fc8 ("Drop wl_drm") has dropped wl_drm, however a lot of
software wasn't quite ready for this (Xwayland, libva, amdvlk).
Keep wl_drm disabled by default to pressure the wl_drm phase-out,
but add a -Dlegacy-wl-drm flag for users to restore the previous
behavior in the meantime.
References: https://github.com/swaywm/sway/issues/7897
|
|
|
|
Now that we use wlr_scene, wlroots handles these. If available use
the wlroots debug options instead.
|
|
|
|
The scene graph abstraction does this for us
|
|
The new scene graph abstraction handles this for us.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is a helper on top of a wlr_scene_buffer that will handle text
rendering for us.
|
|
|
|
|
|
|
|
|
|
|
|
Across a wayland compositor, there are multiple shells: It can be
a toplevel, or a layer_shell, or even something more meta like a drag
icon or highlight indicators when dragging windows around.
This object lets us store values that represent these modes of operation
and keep track of what object is being represented.
|
|
|
|
|
|
This code will be deleted later, but for the time being rename
it so it doesn't conflict with future properties.
|
|
Closes: https://github.com/swaywm/sway/issues/7890
|
|
It is no longer in use.
|
|
Since output layout is destroyed when the wayland display is destroyed
we run into a destroy listener order problem: Either the display starts
destroying the outputs first, in which case we're good: The existing
handling will clean up. However, things go wrong if the display decides
to destroy the output layout first. In this case, sway will hold
invalid references to the output layout as part of each output so that
when it finally goes to destroy them, sway will dereference destroyed
output layout bits.
Ref: https://github.com/swaywm/sway/pull/6844#issuecomment-1843599513
|
|
|
|
This was a input-inhibit concept.
|
|
This is less punishing for users with the Nvidia driver loaded but
not used by Sway (e.g. for CUDA).
|
|
swaynag, swaymsg, and sway do not use this function and are
unlikely to in the future.
|
|
|
|
And the associated background_mode enum.
|
|
|
|
References: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4310
|
|
References: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4440
|
|
As a first step, deny access to privileged protocols to sandboxed
apps.
References: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/3589
|
|
This is now unused.
|
|
Fully reconfiguring all input devices on output change takes a
loooong time. Let's just reconfigure what we need: only mappings
depend on outputs.
|
|
We support the standard idle-notify protocol since Sway 1.8.
|
|
Matches all views. i3 PR: https://github.com/i3/i3/pull/4460
Fixes #7110
|
