This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 36802 - [iOS] UITableViewCellAccessory Partially Hidden When Using RecycleElement
Summary: [iOS] UITableViewCellAccessory Partially Hidden When Using RecycleElement
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS (show other bugs)
Version: 2.3.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-10 00:33 UTC by Jimmy Garrido
Modified: 2016-12-08 00:27 UTC (History)
2 users (show)

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


Attachments
repro project (177.58 KB, application/zip)
2015-12-10 00:33 UTC, Jimmy Garrido
Details
expected result (113.29 KB, image/png)
2015-12-10 00:33 UTC, Jimmy Garrido
Details
actual result Screenshot (105.93 KB, image/png)
2015-12-10 00:34 UTC, Jimmy Garrido
Details

Description Jimmy Garrido 2015-12-10 00:33:12 UTC
Created attachment 14212 [details]
repro project

### Overview
On iOS, when a ListView is using the new RecycleElement caching strategy along with GroupShortNameBinding, the UITableViewCellAccessory added to the cell is partially hidden underneath the jump list.


### Steps to Reproduce
1. Run the attached iOS project


### Expected Results 
See attached “expected result” image. This issue does not occur when using RetainElement.


### Actual Result 
The accessory item is rendered underneath the jump list. See “actual result” image.
Comment 1 Jimmy Garrido 2015-12-10 00:33:48 UTC
Created attachment 14213 [details]
expected result
Comment 2 Jimmy Garrido 2015-12-10 00:34:13 UTC
Created attachment 14214 [details]
actual result Screenshot
Comment 3 Mihail 2015-12-10 07:16:07 UTC
I am also able to reproduce the bug.
Comment 4 Jimmy Garrido 2016-10-25 21:40:40 UTC
Still reproducible with Forms 2.3.3-pre3
Comment 5 Samantha Houts 2016-12-08 00:27:06 UTC
Should be fixed in 2.3.4-pre1. Thank you!

Note You need to log in before you can comment on or make changes to this bug.