I'm using version 9.3.9
When I set the Selected Option Text size to greater than 22px, the displayed text is cut off on the top and bottom in runtime:
However, in composer, the dropdown box and font will grow appropriately:
the same happens in the theme preview mashup. As I increast the Option Text font size above 22px, the Select... HintText in the Dropdown List gets cropped also.
I have tried adjusting every font size in the style theme and even tried the style property overrides for the dropdown widget, but can't find the correct setting to use.
Thanks,
Steve
Accepted Solutions
Hello Steve,
View in the composer and in the browser are two different worlds.
It will be displayed differently in the browser because the browser settings overwrite it with default.
It is more accurate to display the dropdown line height in the browser. I set it to 18px. I assume something similar with you.
With line-height
line-height disabled
I don't see what writes to this value in TWX, which is why the browser uses your default here.
Either way, there is a way to influence it in TWX, which I'm not aware of, or you have to look at how you can influence the browser settings.
hope something could help.
Hello Steve,
View in the composer and in the browser are two different worlds.
It will be displayed differently in the browser because the browser settings overwrite it with default.
It is more accurate to display the dropdown line height in the browser. I set it to 18px. I assume something similar with you.
With line-height
line-height disabled
I don't see what writes to this value in TWX, which is why the browser uses your default here.
Either way, there is a way to influence it in TWX, which I'm not aware of, or you have to look at how you can influence the browser settings.
hope something could help.
Thanks for the tip, TL
I tried the same mashup on our 9.6.1 environment and it displays full size, as expected. The line-height element is disabled, just as you suggested it should be. I tried this on 3 different machines with the same result, so maybe this was a bug fix in 9.6.1?
From our 9.6.1 environment:
