The issue here was that we were no longer preventing default and stop propagation of the native tap event. This casued that in the split editor case we would both react on the tap event which we generate oand on the click event which vrowser generates for the tap.
I have fixed this to prevent default and stop propagating only if I have found a target to wihc hto forward the tap event. I can not blindly prevent since we also realy on native behavior (input boxes getting focused when tapped)

While the split thing works, when I click on a tab close button, the editor closes and opens again.

Pushing to next week when I have a touch laptop.

@bpasero might be a similar issue as #40616
Did you go through the use of .target? I can also take a look

@isidorn yeah good point could be fixed, let me verify when I got a touch device again. I am out tomorrow, so you can also check.

I checked with latest insider on a touch laptop and could not reproduce this any more.

@isidorn nice!