[6.x] Avoid opening Command Palette when Bard field is focused & text is selected

[duncanmcclean]

This pull request fixes an issue where cmd+k to open the Bard link stack conflicts with mod+k to open the Command Palette.

This PR fixes it by opening the link stack when text is selected and opening the Command Palette when it's not.

Fixes #14009

[jasonvarga]

I don't love having Bard code inside command palette. I wonder if there's an alternative.

[duncanmcclean]

I've refactored it to use a callback approach instead...

Statamic.$commandPalette.preventIf(() => {
    const selection = window.getSelection();
    const node = selection?.anchorNode;
    const isInBard = node?.parentElement?.closest('.bard-editor') !== null;
    return isInBard && selection?.toString().length > 0;
});

Let me know what you think.

[jasonvarga]

This works nicely. Thanks.

However since it prevents cmd+k when you have text selected in bard, cmd+k will do absolutely nothing on a mac. No link popover, no command palette.

So I've switched the bard link shortcut back to cmd+k. The only reason we changed it from cmd was because of the command palette conflict. Now that its back to cmd, it matches cmd+b for bold, etc.