You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone) So, the problem is that if you create a room ang give it a long name without spaces, you won't be able to change this name even if you have necessary rights for it, because you won't reach the button "Edit". To prevent some questions, I can't scroll to it, and zooming screen doesn't help either. The only way to fix it is to create another room.
Example:
The way it should be:
What is more, if you go to "Security" in room settings, all content will move out of users view like in that image (same works with "Permissions"):
Reproduction
Go to any space
Create a new room, give it a name that consists of about 100 chars with no spaces (or less, if chars are not all as thin as "i" f.e.)
Go to room settings
Expected behavior
It is expected to have the button for changing name (but you won't see it)
Platform and versions
OS: Windows 10
Browser: Yandex
Cinny: v4.2.3
Additional context
No response
The text was updated successfully, but these errors were encountered:
AdepteXiao
changed the title
It's impossible to edit a large room name
Unable to edit a large room name
Dec 14, 2024
Describe the bug
Hello everyone) So, the problem is that if you create a room ang give it a long name without spaces, you won't be able to change this name even if you have necessary rights for it, because you won't reach the button "Edit". To prevent some questions, I can't scroll to it, and zooming screen doesn't help either. The only way to fix it is to create another room.
Example:
The way it should be:
What is more, if you go to "Security" in room settings, all content will move out of users view like in that image (same works with "Permissions"):
Reproduction
Expected behavior
It is expected to have the button for changing name (but you won't see it)
Platform and versions
Additional context
No response
The text was updated successfully, but these errors were encountered: