workaround for cut-off text in native scroller?

[Klaus major-k]

Hi Brian,

> Am 01.06.2021 um 17:09 schrieb Brian Milby via use-livecode <use-livecode at lists.runrev.com>:
> 
> One thing to try for testing would be to use FSM of empty

Sorry, no idea what "FSM of empty" might be? :-)

> and see how many lines are required.  

Will do, once I know what it means!

> One thing I noticed with browser widget is that native elements render at device resolution inside regardless of FSM in use.  If it requires the same, then this is probably not related.  If the number changes, then I may be on to something.  In either case, having to fudge the height of a text field is not good.

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
klaus at major-k.de