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
wayland-scanner emits a validation warning for protocol/clipreg-cosmic-toplevel-v1.xml:
Element interface content does not follow the DTD, expecting
(description? , (request | event | enum)+), got
WARNING: XML failed validation against built-in DTD
The warning points at the intentionally opaque zcosmic_workspace_handle_v1 declaration:
Bundled protocol descriptions used by the canonical native build should be wire-compatible with the supported COSMIC v1 boundary and valid input to the supported wayland-scanner, without validation warnings.
Investigation / acceptance
Recover the authoritative v1 workspace-interface shape from upstream COSMIC protocol history rather than inventing wire messages.
Preserve the existing design goal: ClipReg binds only the v1 toplevel-info surface it needs and does not pull newer v2/v3 workspace/foreign-toplevel dependencies into the runtime without an observed need.
wayland-scanner client-header and private-code complete without DTD warnings.
make check remains green and generated protocol output remains untracked.
Observed
wayland-scanneremits a validation warning forprotocol/clipreg-cosmic-toplevel-v1.xml:The warning points at the intentionally opaque
zcosmic_workspace_handle_v1declaration:Desired invariant
Bundled protocol descriptions used by the canonical native build should be wire-compatible with the supported COSMIC v1 boundary and valid input to the supported
wayland-scanner, without validation warnings.Investigation / acceptance
wayland-scanner client-headerandprivate-codecomplete without DTD warnings.make checkremains green and generated protocol output remains untracked.This warning is not currently classified as a
v0.2.0-rc.1blocker.