On any CollectionView, the vertical scrollbar is not present until the user hovers/interacts with the UI element in some way. I expected with the VerticalScrollBarVisibility="Always" flag set, the scrollbar would exist upon xaml load, showing the user they could move data up+down without first having to try it themselves.
Steps to Reproduce
Create a CollectionView
Set VerticalScrollBarVisibility="Always"
Expected Result
Scrollbar is shown next to CollectionView upon xaml load and InitializeComponent(); is ran
Actual Result
Scrollbar is invisible until user hovers/scrolls.
Link to public reproduction project repository
No response
Version with bug
8.0.3
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
windows10.0.19041
Did you find any workaround?
No, the user has to attempt to interact before it appears, which isn't the most intuitive UI.
Verified this issue with Visual Studio 17.10.0 Preview 3 (8.0.20 & 8.0.0-rc.1.9171).I can repro it. I need to move the cursor over the content ,the VerticalScrollBar to show up.
Description
On any CollectionView, the vertical scrollbar is not present until the user hovers/interacts with the UI element in some way. I expected with the
VerticalScrollBarVisibility="Always"
flag set, the scrollbar would exist upon xaml load, showing the user they could move data up+down without first having to try it themselves.Steps to Reproduce
VerticalScrollBarVisibility="Always"
Expected Result
Scrollbar is shown next to CollectionView upon xaml load and
InitializeComponent();
is ranActual Result
Scrollbar is invisible until user hovers/scrolls.
Link to public reproduction project repository
No response
Version with bug
8.0.3
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
windows10.0.19041
Did you find any workaround?
No, the user has to attempt to interact before it appears, which isn't the most intuitive UI.
Relevant log output
No response