Wayland Protocols 1.17 Brings Explicit Synchronization & Primary Selection

[M@GOid]

The copy/paste with middle button and change volume with mouse-wheel only are my preferred bragging things when talking Linux to Windows users.

[Hi-Angel]

**Delete the above #10 post**

To delete your post press "Edit", and then "Delete" button.

[varikonniemi]

middle click paste is the only feature i noticed missing last time i tested plasma on wayland. Glad to see it fixed on protocol level.

[Vistaus]

I too hate middle-click-paste. But you *can* actually disable it through GNOME Tweaks (or dconf-editor, whatever you prefer) and KDE System Settings. At least on X11, not sure about Wayland. But some apps are stubborn (I'm looking at you, Vivaldi) and ignore those settings.

[ssokolow]

The copy/paste with middle button and change volume with mouse-wheel only are my preferred bragging things when talking Linux to Windows users.

Those are good, but the one that frustrates me the most when I have to sit down at a Windows PC is when I use the scroll wheel and forget that it'll go to the active window rather than the window under the cursor. Completely brain-dead design decision.

[Anvil]

looks like 1.17 was pulled . i get a 404 error if i click on the download

[rabcor]

Not true - I use both middle-click paste and autoscroll just fine (and to my knowledge, autoscroll in Chrome can only be done through extensions). All you have to do is just middle-click in a place that doesn't have a text input area. Middle clicking in general works fine in Linux in every application, you just get the added bonus of a secondary clipboard. As long as you're aware of this behavior, you'll prefer to have it. I personally find it frustrating to not have middle-click paste.

You're not fucking hearing me, because I was not talking about stupid fucking extensions was I? is it possible to implement both? Probably. can I do that with a fucking bash script and xdotool? no fucking way.

[ssokolow]

You're not fucking hearing me, because I was not talking about stupid fucking extensions was I? is it possible to implement both? Probably. can I do that with a fucking bash script and xdotool? no fucking way.

I got the impression that, when schmidtbag wrote "(and to my knowledge, autoscroll in Chrome can only be done through extensions)", the intent was to say "and, as far as I know, Chrome does something which breaks desktop-provided autoscroll, so you need an extension to overrule that."

Given what I've seen of Chrome's middle-click handling when developing web applications, I wouldn't be at all surprised if Chrome has code which prevents auto-scroll from being triggered "because a web app might want to hang custom behaviour off the middle mouse button".

(Chrome is stupid that way. I have to explicitly write an "if it's not the left button, ignore it" check in my onclick handlers, while Firefox does the sane thing of reserving onclick (which is used for progressive enhancement of links) for left-clicks and letting people who want to customize the middle button use onmousedown and onmouseup instead.)

[schmidtbag]

You're not fucking hearing me, because I was not talking about stupid fucking extensions was I? is it possible to implement both? Probably. can I do that with a fucking bash script and xdotool? no fucking way.

Actually, I hear you loud-and-fucking-clear. Mind explaining what you were talking about at the bottom of this post?:
https://www.phoronix.com/forums/foru...77#post1060777
And yes, it is easy to enable both, without scripts. Since I first started using Linux over a decade ago, I figured out I could use both without having to configure anything.
To my recollection, most programs in Windows didn't allow autoscrolling without an extension either, so as far as I'm concerned, you're complaining about a non-issue and you are getting WAY too hostile over it.

[rabcor]

I got the impression that, when schmidtbag wrote "(and to my knowledge, autoscroll in Chrome can only be done through extensions)", the intent was to say "and, as far as I know, Chrome does something which breaks desktop-provided autoscroll, so you need an extension to overrule that."

Given what I've seen of Chrome's middle-click handling when developing web applications, I wouldn't be at all surprised if Chrome has code which prevents auto-scroll from being triggered "because a web app might want to hang custom behaviour off the middle mouse button".

(Chrome is stupid that way. I have to explicitly write an "if it's not the left button, ignore it" check in my onclick handlers, while Firefox does the sane thing of reserving onclick (which is used for progressive enhancement of links) for left-clicks and letting people who want to customize the middle button use onmousedown and onmouseup instead.)

If that was it then no, I have an autoscroll implementation that works system-wide, and chrome has no problems with it.

To my recollection, most programs in Windows didn't allow autoscrolling without an extension either, so as far as I'm concerned, you're complaining about a non-issue and you are getting WAY too hostile over it.

Windows has system implemented autoscrolling, programs simply need to support it there's no need for an extension, windows's autoscroll works quite well with chrome and several other applications that I use.

Also if you were asking me to give examples of applications where I use autoscrolling... 'Office' software, (some)Instant Messaging, PDF readers, and although rare I sometimes use it in terminal emulators.

And no, you are not hearing me. You literally must have not even read what I wrote.

(And don't throw bullshit at me like how I can enable autoscrolling in browsers with extensions, I use it outside of browsing too, occasionally)

(Read the first half, read it very carefully, because I don't want to have to point it out a third time)
Yet you decided to just ignore that, of course I'd become hostile if you throw me exactly the bullshit I specifically asked not to deal with.

The fact that middle-click pasting can't be disabled through any simple means is not a non-issue. The fact that there is no proper implementation of autoscrolling in neither evdev nor libinput is also not a non-issue. It might not be something you care about, but you are not the sum of everyone.