fix: update remaining wlr-data-control references to ext-data-control

The clipboard bridge backend has been ext-data-control since the
wlr-data-control migration; three comments/log strings still named the
old protocol.  Cosmetic-only, no behavior change.
This commit is contained in:
Andrew Hamilton 2026-09-08 07:08:55 +10:00
parent ccbc782177
commit 1aa9280696
2 changed files with 3 additions and 3 deletions

4
kick.c
View file

@ -5857,7 +5857,7 @@ static void bridge_primary_prefetch_serve(const char *mime, int32_t fd) {
close(fd);
}
/* ---------------- host backend: wlr-data-control ---------------- */
/* ---------------- host backend: ext-data-control ---------------- */
static void bridge_dc_source_send(void *data,
struct ext_data_control_source_v1 *src, const char *mime, int32_t fd) {
@ -7241,7 +7241,7 @@ static void bridge_init(void) {
} else if (bridge.dd) {
bridge.backend = BRIDGE_BACKEND_WL_DATA_DEVICE;
kick_log(KICK_LOG_INFO, "clipboard bridge: focus-based wl_data_device "
"backend (host lacks wlr-data-control; host->nested sync needs "
"backend (host lacks ext-data-control; host->nested sync needs "
"focus; primary selection not bridged)\n");
} else {
kick_log(KICK_LOG_INFO, "clipboard bridge: no host clipboard path\n");

View file

@ -1,6 +1,6 @@
#!/bin/sh
# Throwaway dev wrapper: run a command inside a nested labwc (wlroots-family
# host) so the clipboard bridge uses the wlr-data-control backend.
# host) so the clipboard bridge uses the ext-data-control backend.
# Usage: nested-labwc.sh [--x11] <command...>
# Default command: kick with two wltest tabs.
set -e