ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
i509vcb has quit [Quit: Connection closed for inactivity]
<|>
I'm curious: Accessibility is sometimes an afterthought. Would there be a need for a wayland protocol that allows a client to advertise it is capable of interacting with a screen reader from the compositor? I think most of the time this is done in-app, text-to-speech, like in web browsers. It'd be neat if you could request this functionality from the compositor, but it's likely already part of GUI toolkits
<|>
and I'm just naive.
<|>
When it's part of the GUI toolkit this is great, but I think the distant goal is a screenreader than can do document layout recognition and optical character recognition from surfaces if the GUI toolkit doesn't lend itself at all
<|>
From Windows, I'm only familiar with dragon naturally speaking :>
paulk has quit [Read error: Connection reset by peer]
<MrCooper>
Arnavion: xserver does unlimited buffering on the server side, which obviously has its own issues
sima has joined #wayland
<Arnavion>
Ah
Hypfer is now known as Guest11561
Hypfer has joined #wayland
Guest11561 has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
Company has joined #wayland
rasterman has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
qaqland is now known as Guest11567
Guest11567 has quit [Read error: Connection reset by peer]
qaqland has joined #wayland
mclasen has joined #wayland
Brainium has joined #wayland
Moprius has quit [Quit: bye]
mclasen has quit [Remote host closed the connection]
privacy has quit [Quit: Leaving]
glennk has joined #wayland
mclasen has joined #wayland
leon-anavi has joined #wayland
AnuthaDev_ has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
mclasen has quit []
mclasen has joined #wayland
AnuthaDev has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
AnuthaDev_ has quit []
AnuthaDev has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
manuel1985 has quit [Quit: Leaving]
junaid has quit [Remote host closed the connection]
heapify has joined #wayland
heapify is now known as Guest11579
Guest11579 has quit [Remote host closed the connection]
eroc1990 has quit [Quit: Ping timeout (120 seconds)]
eroc1990 has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
leon-anavi has quit [Remote host closed the connection]
mclasen has joined #wayland
privacy has joined #wayland
gallo has quit [Ping timeout: 480 seconds]
Lacrocivious has joined #wayland
gallo has joined #wayland
<daniels>
Arnavion: why not just increase the socket buffer size?
glennk has joined #wayland
<Lacrocivious>
While an experienced linux user, I am not a coder. I use Fedora Workstation (38 at the moment) with KDE 5.27.9 under X11 and I have a (for me) critical question about switching to Wayland. Namely, focus follows mouse and hover-to-raise action on titlebars. Wayland appears to ignore this and only hover-raises the content window under the titlebar. I stack applications in 'reverse cascade' with the top titlebar beginning at some remove from the left
<Lacrocivious>
edge. The next window is one titlebar width below that and stepped to the left just enough for the application icon to stick out to the left of the top one, so several stacked apps look like stairsteps, bottom left to upper right
<Lacrocivious>
In X11, this allows me to hover over the titlebar icon to switch to that window without clicking
<Lacrocivious>
Rather, to raise that window to active. Apparently I cannot do this in Wayland, and this would basically destroy my working patterns. Is there a Wayland feature to duplicate the X11 behavior in this regard?
<Lacrocivious>
I would appreciate guidance for where to ask this question, as it may not be here
gallo has quit [Ping timeout: 480 seconds]
gallo has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
<kennylevinsen>
Lacrocivious: that's a KDE question as that is a compositor decision they make - it is unrelated to Wayland, the protocol
<Lacrocivious>
kennylevinsen: Thank you for your concisely perfect explanation in response to my excessively loquacious query ;-)