You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reverse engineering the WindowServer to figure out how to implement autofocus I have been able to reconstruct a different workaround to the A B C B focusing issue when multiple displays are in use.
How to reproduce the original problem:
Display 1: Open Terminal (A) and a Chrome window (B)
Display 2: Open a Chrome window (C)
Focus Chrome (B) on Display 1, and then focus Terminal (A) on Display 1.
Try to focus Chrome (C) on Display 2.
When using the accessibility API to focus the window, Chrome (B) on Display 1 would be focused.
After these changes we can now properly focus the Chrome (C) window on Display 2, without having to rely on the scripting-addition.
The text was updated successfully, but these errors were encountered:
After reverse engineering the WindowServer to figure out how to implement autofocus I have been able to reconstruct a different workaround to the A B C B focusing issue when multiple displays are in use.
How to reproduce the original problem:
Display 1: Open Terminal (A) and a Chrome window (B)
Display 2: Open a Chrome window (C)
Focus Chrome (B) on Display 1, and then focus Terminal (A) on Display 1.
Try to focus Chrome (C) on Display 2.
When using the accessibility API to focus the window, Chrome (B) on Display 1 would be focused.
After these changes we can now properly focus the Chrome (C) window on Display 2, without having to rely on the scripting-addition.
The text was updated successfully, but these errors were encountered: