Bug 29718 - targetContentOffset value incorrect within WillEndDragging
Summary: targetContentOffset value incorrect within WillEndDragging
Status: RESOLVED DUPLICATE of bug 29720
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-05-04 15:35 UTC by Cody Beyer (MSFT)
Modified: 2015-05-05 05:49 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 29720

Description Cody Beyer (MSFT) 2015-05-04 15:35:16 UTC
### Description

The following sample app has a simple TableView with some nice items in it. When
scrolling, WillEndDragging has an override to print the targetContentOffset to
console. The value that it prints to console appears incorrect from previous
versions

### Regression Status

Very similar to https://bugzilla.xamarin.com/show_bug.cgi?id=3992

This worked in 8.9.x without incorrect values

### Test Case

https://www.dropbox.com/s/jgwkqf6hvrguyhn/TableEditing.zip?dl=0

### Steps to Reproduce

1. Download and open test case
2. Scroll the list view a drag action

### Expected Results

The values of targetContentOffset written to console should be sizable and
accurate 

### Actual Results

The values of targetContentOffset written to console are incorrect (2.43 etc)

### Version

=== Xamarin Studio ===

Version 5.9 (build 431)
Installation UUID: d8ebdab3-1afa-44d2-8784-4c929811fb0d
Runtime:
    Mono 4.0.0 ((detached/d136b79)
    GTK+ 2.24.23 (Raleigh theme)

    Package version: 400000143

=== Apple Developer Tools ===

Xcode 6.3.1 (7703)
Build 6D1002

=== Xamarin.iOS ===

Version: 8.10.0.267 (Business Edition)
Hash: 6481535
Branch: master
Build date: 2015-04-27 04:38:13-0400

=== Xamarin.Mac ===

Version: 2.0.0.262 (Business Edition)

=== Xamarin.Android ===

Version: 5.1.0.115 (Business Edition)
Android SDK: /Users/beyerc/Library/Developer/Xamarin/android-sdk-macosx
    Supported Android versions:
        2.3   (API level 10)
        4.0.3 (API level 15)
        4.4   (API level 19)
        5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Build Information ===

Release ID: 509000431
Git revision: 7560726734fc7267de2fa9abed2509968deefaa8
Build date: 2015-04-17 19:25:48-04
Xamarin addins: 2e772c734ab3148054eae7bf8949f340fdeb5e5e

=== Operating System ===

Mac OS X 10.10.3
Darwin Codys-MBP.router 14.3.0 Darwin Kernel Version 14.3.0
    Mon Mar 23 11:59:05 PDT 2015
    root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64
Comment 1 Jon Goldberger [MSFT] 2015-05-04 17:56:18 UTC
Just filed another similar bug:
https://bugzilla.xamarin.com/show_bug.cgi?id=29720
Comment 2 Jon Goldberger [MSFT] 2015-05-04 17:58:00 UTC
Might also be related to:
https://bugzilla.xamarin.com/show_bug.cgi?id=14682
which has been in NEEDINFO state fro over a year.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-05-05 05:49:11 UTC

*** This bug has been marked as a duplicate of bug 29720 ***