1878564 - Visual bug in "Sync and save data - Sign In" menu in Polish language

Status: NEW

(Firefox :: Menus, defect)

Description

[u742850]

Attachment: 2024-02-04 15-41-41.mkv

Steps to reproduce:

I open Firefox web browser and quickly click on "Open application menu" button at the right top of the browser window. Firefox UI have to be set to Polish language.

Actual results:

First item at the top of menu is one line height, but after a second it changes to be higher than that, making all next items and the menu itself becoming a bit more longer (please take a look at "Synchronizuj i zachowuj dane" text in the attached screen recording - it becomes two line height after a second).

Expected results:

After first and quick opening menu all items should have fixed height from the very beginning.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Sync' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Ciprian Georgiu, Desktop QA]

I have reproduced this issue with Beta 122.0.1 under Win 11 x64 after changing the language to polish. It seems that the string "Synchronizuj i zachowuj dane" is moved one the second line because the "Zaloguj sie" button is not completely loaded when Firefox is quickly opened for the first time. Give this case, it could be expected.

I'll change this bug to "NEW" for now. Maybe we're going to have an explanation from the developer side for this behavior.

Comment 3

[u742850]

Thanks. I would say that the UI should always remain the same, just the content should change, text should fill in avalaible free space. So for me row with account always should be two-lines height or text should be somehow shorter.

Comment 4

[u742850]

Thanks for reply, please let the appropriate developer know of this bug.

Comment 5

[Ciprian Georgiu, Desktop QA]

(In reply to mrwow042+firefox from comment #4)

Thanks for reply, please let the appropriate developer know of this bug.

I'm not aware of a specific developer available to pick up this issue, but if there's anyone willing to work on this, it will be addressed since the ticket has been triaged and confirmed.