Describe the bug
The autocomplete popup appears to be squished weirdly.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The autocomplete popup should display properly.
Screenshots

Desktop (please complete the following information):
Additional context
I'm using a high DPI display at 150% scaling, which I assume is causing the issue. The web version of the app displays fine.
👋🏾Thanks for opening your first issue here! Be sure to follow the issue template! ✌🏾
Hey @PachowStudios, I'm not even sure I know the steps to reproduce this issue 😄 Would you know of an equivalent way of reproducing this issue on the web for example, assuming that could be universal (I use a Macbook).
@imolorhe I'm only able to reproduce it using the desktop version on Windows. I don't have a Mac so I'm not sure if it happens there too. I assume it has to do with how Electron handles DPI scaling.
I am able to reproduce it in Mac where there is a fresh installation of the client. There is no trivial steps to see what @PachowStudios has shown.
@tangentlin What settings do you have that could make it reproducible?
{
"theme": "light",
"language": "en-US",
"addQueryDepthLimit": 3,
"tabSize": 4,
"theme.fontsize": 24
}
My environment:
I think I can find an easy way to reproduce this by using UI against Github's GraphQL API
Authorization, and value as bearer <paste_token_here>{
user(login: "anyname") {
# Try auto complete here, because there are so many fields, you can see the UI squished the menu items
}
}
Possible cause, perhaps by adding min-height to each menu item the problem would go away.
I still can't reproduce it. What happens when you move through the autocomplete options? I need to get a sense of how to possibly fix it.
I tried 2.1.5 on my other computer, which is a Macbook Pro with Retina Display, it was displaying fine, but as soon as I have updated to 2.1.8 the symptoms come back. The problem seems to happen with GraphQL object that has a lot of fields.
Issue fix is in pull request #785
Looks like that fix did the trick! Working fine on v2.2.0. Thanks guys!
Most helpful comment
Issue fix is in pull request #785