[BUG] openExternal stuck in a loop

Photoshop UXP Plugin API
21

Like that …

await document.querySelector("#dialog_about").uxpShowModal({
                    title: await getLanguageString("str_about")
                  });
22

Hmm, do you have to have await document here ? Are you calling that within an async function ? Of maybe flout menu ?

23

I’ve removed the “await” but it doesn’t make a difference. And yes - that modal dialog is called from a flyout menu.

[EDIT] I called the modal dialog from a panel button, but the problem is still happening. So it might not have to do anything with the modal dialog being called from a flyout.

24

It also happens with “sp-action-button”. However it works with “button”.

25

Try adding at the top of listener callback

evt.preventDefault();
26

What’s your UXP version ?

in the console, type

require("uxp").versions.uxp

27

That didn’t change anything. It seems as if the “click” eventlistener is called again an again. If I set a breakpoint there, it’s triggered whenever I switch from the browser back to Photoshop.

28

My UXP version is … “uxp-5.0.3.86”.

29

I tried the “mouseup” event and that one works.

[EDIT] With “mouseup” even the inline version with “onmouseup” works.

30

Sounds like bug report time :slight_smile:

1 Like
31

I don’t know how to do that. But if a developer stumbles over this, they might want to write that down.

32

I’d simply create a new topic [BUG] ... with all your attempts and findings explained

33

Renaming this thread was easier :slight_smile: I’ve already spent too much time on this one.

34

When using click, you can call evt.target.blur in your handler. This is the same issue w/ opening file dialogs that can get in an infinite loop.

Also, inline event handlers – inline React handlers are fine. Inline non-react handlers will work in some cases, but that’s not intended and will be going away in the future (with a nod to backwards compat, so plugins don’t break surprisingly). All non-react handlers should be added via JS, not via HTML.

1 Like
35

Thanks for the clarification. For now I’m happy with the mouseup solution. Just add this bug to the list.

36

How does blur work for the buttons?

37

Just found out, that the bug also occurs, when the button is pressed from the panel. So it isn’t restricted to the modal dialog. I’ll also have to use mouseup there as well.