xamarin/Xamarin.Forms

[Bug] Visual Material, does not fill the fields with the right indexes

Open

#6,188 opened on May 13, 2019

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
4.1.0a/shell :shell:a/visuale/3 :clock3:help wanteds/unverifiedt/bug :bug:up-for-grabs

Repository metrics

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

Description

Description

When changing the tab, if we change more than 1 tab and we come back, the view is called and the controller is not recovered. I feel that there is a strange behavior with the passage of several tabs. Maybe you have a way to preload them all to avoid this behavior?

Video

Sorry for the sound 2019-05-13-16-46-13 by Game Genie.zip

Reproduce

  1. Change the content of the Entry
  2. Go to Fake1 page and return to the MainPage
  3. Size of the entry have no changes
  4. Go to Fake 2 and come back to the main page
  5. Entry size have change Normal?

ShellNavigationForm.zip

EDIT After several hours of research, I understood several things and managed to reproduce the problem.

  1. The bug only occurs with Xamarin.Forms.VIsual.Material in a page in Visual = "Material"
  2. The bug does not empty the fields but dump the content of the last field in the previous field, which itself flows into the previous field, and so on.

Here is an example for the reproduction: bug_repro.zip

You can watch that? Thank you.

Contributor guide

Research direction
Investigate the tab navigation lifecycle in Xamarin.Forms Visual Material, focusing on how views are created and restored when switching tabs. Look for issues with field indexing and state persistence.
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.
Mostly clear
Prerequisites
C#Xamarin.FormsMobile development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60