Some settings not fully visible
Hi,
I can't tell if this is since the lastest beta or has been there before. But some settings screens do not fit on the screen and the windows do not allow to scroll to the bottom of them, so the content is not readable.
Maybe this is related to the German translation.
1Password Version: 8.6.0
Extension Version: Not Provided
OS Version: Windows 10
Comments
-
Hello @Manaburner, thank you for letting us know about this - and our apologies for the graphical strangeness!
A few questions for you:
- Does adjusting the window size make any difference?
- In the Appearance tab, what is your zoom level currently set to?
These questions will help us verify the nature of the issue and get a fix in place sooner. Thanks again for reporting it!
ref: dev/core/core#12397
0 -
In the Appearance tab, what is your zoom level currently set to?
There is no setting for the zoom level in 8.6.0-26 beta build. 😕
Maybe this is related to the German translation.
I don't think so. I'm also using the German translation and have the zoom level set to 2x "STRG + +". For me it looks good in the settings.
But I'm on Windows 11.
0 -
Does adjusting the window size make any difference?
I have the 1Password App itself on fullscreen. I cannot resize the settings screen, if that is what you're asking for.
In the Appearance tab, what is your zoom level currently set to?
I also don't have a zoom level setting available.
What screen resolution are you using? I'm on a 14'' notebook with 1920x1080
0 -
What screen resolution are you using? I'm on a 14'' notebook with 1920x1080
I'm using a screen resolution of 2560x1440, but sized the 1Password window to 1920x1200.
On my Laptop, I'm running 1Password 8 in full-screen with 1920x1080 without any zoom level.
Here I can see that only the advanced setting doesn't fit.
0 -
Hi folks, thank you for the additional details on this. I've gone ahead and reported it to our developers for further investigation. We appreciate you letting us know so we can track down the specifics and address the issue!
(and hey, this is my 1,000th community reply! woohoo 🥳)
ref: dev/core/core#12920
0 -
0
