Expansion elements crawled out of the expansion screen

podkopaev

Starting approximately from version 1.23.2.beta (perhaps this clarification is not related to the cause of the problem) expansion elements crawled out of the expansion screen.

Google Chrome 88.0.4324.146 (Stable)

---

1Password Version: Not Provided
Extension Version: 1.24.1.beta
OS Version: Windows 10
Sync Type: Not Provided

ag_yaron

Hey @podkopaev ,

Are you using screen scaling in your resolution settings? Or is Chrome set to use zoom larger than 100%?

ref: dev/core/core#4703

podkopaev

@ag_yaron

The default scaling of 100% is used everywhere.

ag_yaron

Thanks for confirming @podkopaev .

We'll try to investigate the matter. If we need anything else we will contact you here :)

podkopaev

@ag_yaron

I noticed a peculiarity: when I open an extension window on an empty (default) browser tab, the window is displayed without problems.

ag_yaron

@podkopaev

If you change the extension's language to English, is the problem resolved? You can change it by going into the extension's settings.

podkopaev

@ag_yaron

After changing the language, there is no problem.

(but earlier there were no problems for the Russian translation)

ag_yaron

Hmm.

If you switch back to Russian the issue persists, right?
I'll have the team look at this when possible. I can't seem to be able to reproduce the issue though, hopefully one of the developers can.

podkopaev

I remind you of my problem and inform you that it is present in version 1.24.4.beta :)

ag_yaron

Thanks for the reminder @podkopaev .
We've had some other users reporting it as well so I do hope it will reach the top of the queue for our developers in the near future.

Feel free to keep reminding us here as you see fit :)

podkopaev

I remind you of my problem and inform you that it is present in version 1.25.4

ag_ana

Thank you for the reminder @podkopaev :+1:

podkopaev

I remind you of my problem and inform you that it is present in version 2.0.

When will the queue come up before it is fixed?

:|

ag_yaron

Thanks for checking the latest version @podkopaev .

I'll let the devs know it is still an issue in hopes they'll have the time and resources to address this sooner rather than later.