Community
Participate
Working Groups
It seems like ScrolledForm has number of issues that makes it hard to deal with nested composites that need to fit to the width of the editor or use layout like RowLayout (which wrap component automatically to fit to width). Probably it would be a good idea to instead use regular Form with the nested ScrolledComposite, which doesn't have such issues.
Rob: consider this when working on task editor layout.
Please increase priority of this one. It has huge impact on JIRA editor layout and also practically main obstacle to make task editors to shrink to the narrow width (i.e. can't use rowlayout for header section).
Our editor pages are based on ManagedForm which only uses ScrolledForm so it doesn't appear that we can avoid this.
Rob, please reconsider. Scrollable composite is a major showstopper for many UI issues.
Can you give me more details as to what problems this is causing... perhaps we can come up with another work around?
