I have mashup which uses Collection widget to display multiple inner mashups. I just found the page cannot scroll in Android Pad + Chrome. In the development mode there is a toolbar on top of the screen which allows you to adjust the screen size, the responsive mashup cannot scroll if it's "Full Screen", it can only works if set it to others like "iPad Landscape". In the production mode, there is no such toolbar , I've set the screen size to "iPad Landscape" in Thingworx composer , but it doesn't work. It seems that the page always act as "full screen" size.
I also tried the other combination, like Android Pad + Firefox , iPad + Safari, iPad + Chrome. The page can scroll well for all of these combination even though the page size setting is "full screen" in composer. But my customer only use Android Pad and Android Pad + Firefox has some other issues (like the click event of value display widget doesn't has response, maybe more ), so Android Pad + Chrome is my only choice .
Set the "ScrollbarType" to "Always on" doesn't help . Any suggestion ? It's critical as Collection widget, not like the other widgets , it acts as a repeatable widgets container for display complex table/flex view , there is no replacement of the widget.
The problem can be reproduced using the attached file, it's actual the offical Collection widget teaching sample from https://community.ptc.com/t5/IoT-Tech-Tips/Reimagine-your-Application-UI-with-Collection-and-CSS-in/... .
Thingworx 8.4.2 + Postgresql 10.x + Tomcat 9.x
In researching this issue, I found that we have an existing case with R&D. At this point in time, a target date for resolution is not yet available.
Have you tried creating a non-responsive mashup as a workaround?
Yes, I tried it . The static mashup could be workaround , but then I have to create two mashups for every mashup which use collection widget, one for PC and another one for Pad . and the browser won't go to "full screen" mode automatically when scrolling down.
It's better to raise the priority of this issue.
This issue has been accepted as a bug but time does not allow for it to be included in the upcoming release due out in the next several days. It has been targeted for the following release.
I will keep this post open in the meantime for follow-up as we move closer to the next release date.