When an application-specific Acrobat dialogue pops up, it isn't forced to the front and disables the application interaction until dealt with. This is somewhat normal but doesn't work in practice.

Took me a while to figure out, but I'll skip the who and why and let others decide how to deal with this disability. Feel free to suggest nut-behind-the-wheel solutions.

I launch Acrobat reader, either doc or app, and use the keyboard to immediately open the search tool to find a word. That word is found, but the word is inside a link so it generates a dialogue asking if I want to go to the link - I do not. This is slower real-time than anything I'm interacting with, and I've already moved on to another application to find that Acrobat is giving me system error beeps and locked up. I have to kill it to start over.

Assumption: the open-link dialogue is behind the Acrobat file page view, now impossible to interact with and I can't move the window aside. I don't understand why the dialogue isn't in front of the page view. Should it be? Is there some behaviour of switching to a different app circumventing the stacking of windows? Shouldn't everything attached to the application behave as if inside it's own galaxy of the Windows universe? This reminds me of the bad old days when every pop-up was a window and I had to cycle through them all to get the one I want to the foreground, no longer an option.

This can't be right but I have no idea why and would love suggestions, workarounds, or bug-fixes. Blocking all link access didn't help, and keep in mind I have no idea if the dialogue is actually behind the page view, it is intuited; I didn't identify any particular process for the dialogue. This didn't happen before, so what changed?

Another thought: maybe it's locking up before it even finishes rendering the dialogue? The one time I did see the dialogue was after a long delay, popping to the front after switching apps multiple times.