Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Autocomplete suggestion box appears underneath floating iTerm window #19

Closed
jayrhynas opened this issue Jan 25, 2021 · 6 comments
Closed
Labels
type:bug Something isn't working

Comments

@jayrhynas
Copy link

Summary:
Autocomplete suggestion box appears underneath floating iTerm window

Steps to Reproduce:

  1. Create an iTerm hotkey window profile
  2. In iTerm preferences, under Profile > Keys > Configure Hotkey Window, enable the Floating window setting
  3. Trigger the hotkey window, then start typing a command that triggers the Fig autocomplete suggestion box.

Expected Results:
Autocomplete suggestion box appears on top of iTerm window.

Actual Results:
Autocomplete suggestion box appears under iTerm window (although it remains interactive).
Autocomplete suggestion box also does not dismiss when dismissing hotkey window.

System information:
OS: MacOS Big Sur 11.1
Terminal: iTerm2 (3.4.3)
Version of Fig: 1.0.32 (B80)

Additional Notes:
Screen Shot 2021-01-25 at 10 07 55 AM

@jayrhynas jayrhynas added the type:bug Something isn't working label Jan 25, 2021
@brendanfalk
Copy link
Member

brendanfalk commented Jan 25, 2021 via email

@jayrhynas
Copy link
Author

The main difference is with Floating window turned on, you can open the hotkey window over full screen applications. If it's turned off, triggering the hotkey while in a full screen app will change your space to a non-full screen one before showing the hotkey window.

For now I have disabled the setting though to try out Fig.

@brendanfalk
Copy link
Member

brendanfalk commented Jan 25, 2021 via email

@jayrhynas
Copy link
Author

Ah yes it doesn't take effect until restarting, I ran into the opposite issue when I enabled it in the first place.

@mschrage
Copy link
Member

This will be fixed in the next build!

@mschrage
Copy link
Member

Fixed in v1.0.33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants