Windowscommunitytoolkit: PullToRefreshContent & ReleaseToRefreshContent different behaviour on mobile an desktop

Created on 15 Mar 2017 · 6Comments · Source: windows-toolkit/WindowsCommunityToolkit

Given this template

<Style TargetType="uwpControls:PullToRefreshListView">
    <Setter Property="PullToRefreshContent">
        <Setter.Value>
            <TextBlock Text="&#xE112;"
                       FontSize="28"
                       Height="30"
                       VerticalAlignment="Bottom"
                       FontFamily="Segoe MDL2 Assets"
                       Margin="0,0,0,10"
                       RenderTransformOrigin="0.5,0.5">
                <TextBlock.RenderTransform>
                    <RotateTransform Angle="-90"/>
                </TextBlock.RenderTransform>
            </TextBlock>
        </Setter.Value>
        </Setter>
    <Setter Property="ReleaseToRefreshContent">
        <Setter.Value>
            <TextBlock Text="&#xE112;"
                       FontSize="28"
                       Height="30"
                       VerticalAlignment="Bottom"
                       FontFamily="Segoe MDL2 Assets"
                       Margin="0,0,0,10"
                       RenderTransformOrigin="0.5,0.5">
                <TextBlock.RenderTransform>
                    <RotateTransform Angle="-90"/>
                </TextBlock.RenderTransform>
            </TextBlock>
        </Setter.Value>
    </Setter>
    <Setter Property="PullThreshold" Value="80"/>
    <Setter Property="OverscrollLimit" Value="0.2"/>
</Style>

When i run on desktop I get the expected behavior of the TextBlock

animation

But when on Mobile it doesn't align to bottom. I removed the margin but it didn't help.

animation3

I tried de default value for those fields and the result is the same.

animation2

Both Mobile and desktop are running the same Windows build (10.0.14393.953)

bug controls in progress

Source

rpedretti

All 6 comments

No response from the community. ping @nmetulev

windowstoolkitbot on 7 Oct 2017

I guess it can be closed since MS is not supporting mobile anymore

rpedretti on 8 Oct 2017

👎1 👍1

This is a behavior difference issue of mouse vs touch, I can verify the same behavior in the sample app on desktop. However, per #1465, this control is getting deprecated in the next release due to a it being available in the Fall Creators Update and this will not be prioritized.