You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for bringing this to my attention. We should certainly add support for it.
That being said, I am quite disappointed that this protocol was standardized without as much as cc'ing the [one of the] primary client-side user[s] of the wlr-data-control protocol. (Nor, from looking at the MR, were other clients' developers notified?). Don't you need (multiple?) client-side implementation(s) for a protocol to be accepted? Aren't you interested in the feedback we might have?
And I do have suggestions indeed, ones that I gave up on getting past the wlroots folks. A new neutral protocol under the Wayland governance could have been a great time to bring them up again.
I was unaware of clients to reach out to (I had, perhaps wrongfully assumed that the w-p MR alone would let stakeholders know it was ongoing). I started doing this after it landed as I'm working through the backlog of custom protocols used by KDE. Sorry about that.
wlr-data-control-unstable-v1
has been superseded withext-data-control-v1
in wayland-protocols, and will be included in wayland-protocols v1.39.Please add support for
ext-data-control
so that this works with compositors that only support the standardized extension.The text was updated successfully, but these errors were encountered: