25
"focus stealing" ought to be a solved problem by now... (lemmy.ca)
submitted 6 months ago by to c/nowhereelsetoshare@sh.itjust.works
8 comments fedilink hide all child comments
 

It seems to be, that the rule ought to be:

  • "if the operator's mouse/keyboard event which originally spawned the new window is still the last one generated, then it may grab focus"

In other words, if the user is WAITING on a window to pop up, then it takes focus. But otherwise (such as the user typing in another document) it does NOT take focus.

Of course, in this context, I refer to only key-down and mouse-down events, not passive events like mouse movement.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 6 months ago

depending on type of window management it can appear above another window under your mouse cursor, in which case it stole the focus. imagine you're about to click a download button and instead a window with a delete prompt appears above the button and you confirm that instead. my point is: focus settings alone don't fix this.

  • permalink
  • fedilink
  • source
  • parent