xamarin/Xamarin.Forms

[iOS] ListView ItemSelected fires when selecting group header row

Open

#3,587 opened on Aug 16, 2018

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
a/listviewe/5 :clock5:help wantedinactivep/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

https://www.screencast.com/t/jj1GyFynx

When selecting the group header, the first row in the group is selected. This is not the expected behavior and does not occur on the first group section.

This does not happen on Android.

Steps to Reproduce

  1. Select the group header of the first section and notice the ItemSelected event does not fire.
  2. Select a row and notice it does.
  3. Select the second section group header and notice it fires.

Expected Behavior

Selecting group headers should not fire ItemSelected for the first row in the group

Actual Behavior

ItemSelect fires and first row of group is selected.

Basic Information

  • Version with issue: 3.1.0, 3.2-pre2
  • IDE:
  • Platform Target Frameworks:
    • iOS: 12.0, deployed to 12 and 11.4

Reproduction Link

Archive.zip

Contributor guide

Research direction
Investigate the iOS ListView renderer to understand why the group header selection triggers ItemSelected for the first row. Focus on the UITableViewController and its delegate methods, particularly RowSelected and the data source handling of section headers. Check if the issue is related to the reuse of header cells or incorrect index calculation.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Xamarin.FormsiOSC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75