CAJA 'Split pane' Action is broken for 'Caja-actions' for Caja 1.28 in Fedora 43

[SGill1952]

Fedora 43 Mate, kernel: 6.18/4-200.fc43.x86_64
Added an action to Caja actions to toggle splitting the pane, setting a Caja menu/toolbar item so as to be able to split the pane using the mouse rather than the keyboard.

In Caja v 1.26.4, it works fine.
In Caja v 1.28.0, it's broken.

Used the Caja-Actions tool to add the action (the tool is also version 1.28.0):
Command [ Path: /usr/bin/xdotool Parameters: key "F3" Working directory: %d ]
[Have used this command for many years, through more than half-a-dozen successful Fedora Mate upgrades.]

Note that toggling the F3 key does split/unsplit the pane, the action expected for the command.
This works, but is inconvenient.

Other actions continue to work as they have in the past:
New folder, New Tab, Show hidden
All using xdotool, and all work as expected.

I first noticed this in a VM for Fed434Mate that I spun up several months ago. A few weeks later, I updated an HP laptop to that system and the problem was present, and it persists even with the latest system updates.

[lukefromdc]

There are so many changes from 1.26 to 1.28 this could be anywhere. Note that this is not even a use-case some of us could anticipate, you note the internal code for caja's dual pane mode as controlled from the menu works fine. I just tested that and it works even under the wayland session. I know a bisect would be a lot of work for you with all those commits but it might be the only way to identify the issue and determine whether an issue was introduced in caja itself or the tool itself (for which you did not post the code) needs to be updated. Any time an application is developed that uses an undocumented feature (one that exists by chance and is not maintained) of another program this sort of thing can happen. No idea if your tool does or not. Possibly the syntheszed mouse or keyboard events are no longer properly captured? Also you would need to test 1.28 and 1.26 back to back in the same OS with no other changes (might have to do local builds for this) to verify no underlying library like glib or gtk introduced this.