We've reproduced the scenario. The described behavior is caused by a peculiarity of ScrollViewer
- it perceives each group as a separate item that takes part in scrolling and if there's only one group, it wouldn't scroll, disregarding the number of items in the group. Whether an element is allowed to scroll or not, is controlled by the value of CanContentScroll
property - if it's "True", the ScrollViewer
scrolls in terms of logical units (item-by-item); if it's "False", the scrolling is in terms of physical units (pixel-by-pixel). The default value for CanContentScroll
is "True", so if there's only one group, scrolling would not be available. Setting the value of this property to "False" would do the trick:
Doing this, we break visrtualization, but in cases where a container that doesn't support virtualization is used (like WrapPanel
) it doesn't cause any harm.
Hope this helps.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items