i3 is sending non-existing WORKSPACE(focus) events to IPC clients when moving containers.

[Iskustvo]

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

Moving container from current workspace to some other workspace(both existing and non-existing) triggers i3 to send WORKSPACE(change = focus) event, but focus from the user's perspective stays unchanged.

Expected Behavior

i3 doesn't send misleading WORKSPACE(change = focus) events when focus from the user's perspective stays unchanged.

Reproduction Instructions

Easily observable by using i3-msg.

1. Open two terminals in same workspace.
2. In one terminal, subscribe to WORKSPACE events:

i3-msg -m -t subscribe '[ "workspace" ]'

3. In second terminal send the move command:

i3-msg move container to workspace some_name

4. Observe the output from the only terminal that stayed on the current workspace.

If workspace some_name already existed, there will be 1 WORKSPACE event - focus event indicating that the focus has changed from current workspace to some_name workspace, but it hasn't.
If workspace some_name didn't exist, there will be 2 WORKSPACE events, one claiming that workspace some_name is being created(which it is) and again, a focus event claiming that focus has changed from current workspace to newly created some_name workspace, but it hasn't.

Environment

Output of i3 --moreversion 2>&-:

i3 version: 4.17.1 (2019-08-30)

[i3bot]

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)