Closing suggestions programmatically can trigger other

[oBusk]

Affected Packages

suggestion

Version(s)

3.20.1

Bug Description

Trying to write code to close suggestion when editor is blurred, a behaviour I feel like could be the default, I ran into an issue where it was closed but then immidiately opened. I realized this was because exitSuggestion(editor.view, pluginKeyA) would trigger the findSuggestionMatch code for pluginKeyB

So I was calling exitSuggestion() multiple times to make sure all potential suggestions were closed, and after closing A, when I called exit on B, it triggered findSuggestionMatch() for the first one and opened it again.

Browser Used

Firefox

Code Example URL

https://codesandbox.io/p/devbox/reverent-neumann-cx4nrg?workspaceId=ws_VrZDLHe5kHRsi7kpJ6PqyE

Expected Behavior

I expect that triggering exitSuggestion() for another suggestion should not count as a triggering transaction

Additional Context (Optional)

This is trying to use the API introduced in #6833

Dependency Updates

• Yes, I've updated all my dependencies.

[oBusk]

I can clarify a few things

• I understand that my example is pretty bad because closing on blur means you can't use your mouse to click suggestions (clicking triggers the exit before the suggestion is picked),
• It might be expected that you only ever call exitSuggestions() if it is already active, if so fine to close ofc.

So workaround is

if(pluginKey.getState(editor.state).active) {
  exitSuggestion(editor.view, pluginKey)
}

[oBusk]

I looked at implementing a fix (#7595), but there's no sleek way to do it, understand if closed as not-a-problem.