Safari: Fix an unexpected input selection

[GogoVega]

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Proposed changes

Partial fix of #4463.

When double clicking on a node to open the edit box, the palette filter input is selected (blue background). Visible on the video in the linked issue.

It's the same behavior if the double clicking is done in a container (editableList), one of the inputs will be selected.

Checklist

• I have read the contribution guidelines
• For non-bugfix PRs, I have discussed this change on the forum/slack team.
• I have run npm run test to verify the unit tests pass
• I have added suitable unit tests to cover the new/changed functionality

[knolleary]

Applying this at such a top-level container is risky in terms of side-effects.

I see that Safari still requires the -webkit prefix. I would suggest the first pass should look for all existing instances of user-select and add the -webkit-user-select rule alongside it. That should then mean we have a consistent baseline. Then we can look to see if something additional is needed for Safari.

[GogoVega]

Ok, I look at this 😉

[GogoVega]

I will convert it to a draft because it will take a little time. i.e. The palette has the disable-selection (user-select for all env) attribute disabled but when I double click on the workspace the filter is selected...