Attributed metadata history
Up to 100 retained publisher events per page for 5ca86577336d165ccff8d2ab02e98c07e228c9e11b522f990bfe395abe715f8e. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_ad89769b9e64591ab5
observed · 2026-10-12 14:01:03 UTC
One of the biggest sore points with Wayland is its focus stealing protection. The idea is good: an application should not be able to bring itself into focus at an unexpected time, only when the currently active application allows it. Support is still lacking however, which might also be due to Gtk/Glib implementing the required XDG activation protocol but not really documenting it. It took me a bit of time to figure this out without any public information, this article will hopefully make things easier for other people. Contents How the XDG activation protocol works State of implementation in Gtk/Glib Starting applications via Gio.AppInfo Starting applications by other means How the XDG activation protocol works The main idea behind the XDG activation protocol is that focus transfer from one application to another requires consent. With X11 a file manager could just launch the browser for an HTML file and the browser would immediately take focus, even if that browser was already running. With Wayland the file manager has to indicate that the browser is allowed to take focus. It does that by giving the browser its XDG activation token, typically via XD
Fingerprint: fc8b77a1e0558bf660fcbf70a4377a2dc21c9ab11720c175d725203811fd4a9d
intelligence_src_ad89769b9e64591ab5
observed · 2026-10-12 14:01:03 UTC
available
Fingerprint: 05d146f940ea021a0ff67bda626eeffcdf1f2ccbc0f3c3114fff19b0a80eeaf4