[SOLVED]The name of the device is not visible and makes it difficult to edit

[olaein 1]

When you go to device, you can see the editing box but no content, which makes it difficult to edit names

If open device you can se the name in family member but it no help when edit name

I am user of Fibaro more than 10 years

My computer is Windows 11 and i use chrome web-reader Version 123.0.6312.124 (Officiell version) (64 bitar)

Please login or register to see this attachment.

Edited April 22, 2024 by olaein
Attache picture to explain 1, edit box and 2, name of family

[awlieser 19]

Yes, it‘s a nuisance that you can only see the first 3 letters (or so) of the device name. Maybe Fibaro should enlarge the Name column - but there will be tradeoffs ☹️Cheers Alfons

[m.roszak 763]

Could you paste here some screens to help me understand what is the issue here?

[olaein 1]

I have picture in my orginal message now!

[SmartHomeEddy 1,005]

I can only get that field so small, if I put my window very small

 

Please login or register to see this attachment.

 

Please login or register to see this image.

/monthly_2024_04/image.png.aa2761af724f530c0b076641fe27ea32.png" />

 

 

[m.roszak 763]

How many px in width does your screen have?
Looks like really narrow, web interface works correctly with a 1024px minimum.

Are you using any built-in zoom in the browser?

On chrome:

1. This is how it looks on 1280px:

Please login or register to see this image.

/monthly_2024_04/image.png.384275c4311cd58acb0d3335e35028e1.png" />
2. on 1024px (left manu automatically collapsed then):

[olaein 1]

I have a 5k screen and usually have a resolution of 5120px but have now reduced to 3440px giving 1720px for a split screen which is how I work.
But you point to the right impact as my browser was also set to display 150%.
I have accidentally changed the resolution and magnification in the browser at the same time depending on what I was working on.
The result was that just under 1700px was not enough to display the name field.
Thanks for the solution I didn't understand at the time, now it works fine when I set the browser to 100%