Strangely, could not work around it by adding a second action Unfocus

    <keybind key="C-W-1">
      <action name="SendToDesktop" to="1" follow="no" />
      <action name="Unfocus" />
    </keybind>
    <keybind key="C-W-2">
    ...

...and putting Unfocus first makes it the only action applied to the window. So each action in the keybind checks for a focused window, not a single check per keybind?

If you unfocus first how does it know which window to send?

And yes, each action checks things for itself, the actions are not chained, just executed one after another.

Window is somewhere else, but still receives input.

Thanks for the report. We should indeed focus the then topmost window on the current workspace.

Why does sending+unfocusing workaround not work? Window is still focused, so Unfocus action should apply, but it does not. Could be an indication of a hidden bug.

From a quick look in the code, Unfocus only resets the keyboard focus, it will not focus the topmost surface. So further input should then not be relayed to the now hidden window. Is that actually the case?

Yes, input stops, and no other window is focused.

Usable workaround: add NextWindow action.