IScroll Provider Anchor
IScroll Provider Anchor
IScroll Provider Anchor
Specifies a contract for a scrolling control that supports scroll anchoring.
public : interface IScrollAnchorProvider
public interface IScrollAnchorProvider
Public Interface IScrollAnchorProvider
Windows 10 requirements
Windows 10, version 1809 (introduced v10.0.17763.0)
Windows.Foundation.UniversalApiContract (introduced v7)
Scroll anchoring is when a scrolling control automatically changes the position of its viewport to prevent the content from visibly jumping. The jump is caused by a change in the content's layout. The scroll anchor provider applies a shift after observing a change in the position of an anchor element within the content.
It's the responsibility of the implementing scroll control to determine what policy it will use in choosing a CurrentAnchor from the set of registered candidates.
When a layout change impacts the size/position of the anchor element, the viewport should automatically shift to maintain the previous position of the anchor element relative to the viewport.
Scroll anchoring (i.e. an automatic viewport shift) doesn't apply at all times. It should happen as a result of candidate elements being added to or removed from the tree or changing in size. Other situations that may trigger a layout pass, but do not necessarily cause automatic viewport shifts would include:
- A user panning the content
- A developer programmatically changing the view
- Handling a BringIntoViewRequested event
The Anchor Element
The implementing control should choose an anchor element from the set of previously registered candidates and set it as its CurrentAnchor.
Candidate Anchor Elements
The set of candidate anchor elements may change during any of the situations called out previously. Elements are registered as potential anchor candidates by:
- setting their UIElement.CanBeScrollAnchor property to true, or
- programmatically registering the element using the RegisterAnchorCandidate method.
The CanBeScrollAnchor property can be set at any time. When set, the framework implicitly calls RegisterAnchorCandidate /UnregisterAnchorCandidate, but only on the first IScrollAnchorProvider found in that element's chain of ancestors.
The framework similarly registers/unregisters elements with CanBeScrollAnchor set to true as they are added or removed from the live visual tree. But, once again, it is only done with the first IScrollAnchorProvider found in the element's chain of ancestors.
A virtualizing control may choose to automatically set the CanBeScrollAnchor on its generated children elements.
ScrollViewer: An Example
The ScrollViewer control performs scroll anchoring during its ArrangeOverride. It raises an AnchorRequested event at the beginning of ArrangeOverride, which provides you with an opportunity to explicitly specify the anchor element. Otherwise, it chooses a candidate in the viewport that is closest to a viewport-relative anchor point and then sets that element as its CurrentAnchor.
The anchor point comes from the HorizontalAnchorRatio and VerticalAnchorRatio properties. When the ratios are zero (default), the anchor point is the top left corner of the viewport (assuming the FlowDirection is LeftToRight). If the ratios are both set to 0.5 then the anchor point is the center of the viewport. Similarly, when the ratios are both 1.0 then the anchor point is the bottom right corner of the viewport.
Special Case: Anchoring at the edge
The beginning or end of the scrollable content represents a special anchor scenario. For example, consider the expected behavior when a user in an email application has vertically scrolled down the list by some amount. When a new message arrives it is inserted at the top of the list (outside the bounds of content the user currently sees). What the user currently sees should not suddenly jump to a new position due to the arrival of a new message at the top of the list. However, if their current scroll position is at the top, then the existing content should appear to shift down to make room for the new message.
The inverse scenario is a chat experience. When the user is scrolled to the very bottom and a new message arrives the content should appear to shift up to make room to display the new message. In reality, what happens is that the viewport needs to shift down to track the new end of the scrollable content. When the user is not scrolled to the very beginning/end of the content, then the position of the viewport with respect to some visible content that is considered "interesting" should remain in sync (i.e. anchored).
The ScrollViewer treats the values of 0.0 and 1.0 for the HorizontalAnchorRatio and VerticalAnchorRatio properties with special behavior. If both the value is 0.0 and the user is scrolled to the start, then the start position is used as the anchor instead of an anchor candidate. Similarly, if both the value is 1.0 and the user is scrolled to the end then the end of the content is used as the anchor. If the position of the end grows due to size changes then the new end is used.
|CurrentAnchor CurrentAnchor CurrentAnchor CurrentAnchor||
The currently chosen anchor element to use for scroll anchoring.
|RegisterAnchorCandidate(UIElement) RegisterAnchorCandidate(UIElement) RegisterAnchorCandidate(UIElement) RegisterAnchorCandidate(UIElement)||
Registers a UIElement as a potential scroll anchor candidate.
|UnregisterAnchorCandidate(UIElement) UnregisterAnchorCandidate(UIElement) UnregisterAnchorCandidate(UIElement) UnregisterAnchorCandidate(UIElement)||
Unregisters a UIElement as a potential scroll anchor candidate.
- ScrollViewer.E:Windows.UI.Xaml.Controls.ScrollViewer.AnchorRequested - P:Windows.UI.Xaml.UIElement.CanBeScrollAnchor - E:Windows.UI.Xaml.UIElement.BringIntoViewRequested - M:Windows.UI.Xaml.UIElement.RegisterAsScrollPort(Windows.UI.Xaml.UIElement)