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

[MaxenceSAUNIER]

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.

[MaxenceSAUNIER]

Ok, I have edit my first post. I managed to get more informations.

[MaxenceSAUNIER]

Any news ?

[SteveGrixti]

Hi,

This is turning out to be a big issue for me.

I have a form on my android application that consists of 8 tabs. As soon as I skipped the 5th tab, it is hiding the bound values on the first tab even though they are still attached to the bindingcontext. Then, when I move onto the 6th tab, it hides the bound values of the second tab, and so on and so forth.

Same issue as @MaxenceSAUNIER .

Is this being looked at?

Thanks.

[SteveGrixti]

Hi,

This is turning out to be a big issue for me.

I have a form on my android application that consists of 8 tabs. As soon as I skipped the 5th tab, it is hiding the bound values on the first tab even though they are still attached to the bindingcontext. Then, when I move onto the 6th tab, it hides the bound values of the second tab, and so on and so forth.

Same issue as @MaxenceSAUNIER .

Is this being looked at?

Thanks.

UPDATE:

Just to let everyone know, I managed to get around this by making use of the Android specific method SetOffscreenPageLimit() as shown below. Issue no longer occurs.

Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());
Children.Add(new Page());

On<Android>().SetOffscreenPageLimit(10);