The reason why it is truncated is because of the list widget. I see what you're trying to do. Here are some suggestions. It seems you're trying to keep the user on one page if that is correct then you can put the map and list inside a section and have the list contain a button to display more information inside a feature info widget. You could custom the popup in the webmap and save it to the layer so it only shows the information you need in the feature info. You section would have two views, list and map, and feature info and map. This would also eliminate the need for the text widget on the map since there is a lot of text to display. I hope this helps.
Hi David Martinez,
Thanks so much for the reply above!
With your new Windows functionality I think there will be a lot more potential for this app. That being said, I'm still seeing the truncation issues even when following your above recommendations in the Windows. Are there any other solutions for this or am I experiencing a bug?
I did more digging into the configuration of the Window and it appears it's being used with a Column widget which as a "scrollable" setting- but that's not all- the text box added to this widget then requires a randomly large height to ensure that all the text get's included and not truncated.
When setting the text to "auto" per your prior suggestion, the text still is truncated.
Is there a way that a scroll setting could be added to the text widget for ease of use versus all of this configuring?
There is no such a way of adding a scroll setting to the text widget.
The "auto" is working for the text widget. But the text's display area is also restricted by its parent container, such as page, window, or list if you put the text into one. So, when you use "auto", you need to make sure there is enough space to display the content.