[Gallery][iOS/Android][CheckBox] Wrong initial Foreground color for the text in the sample pages about uno.gallery

[jeromelaban]

What's the impact of setting material last (other than working around the issue)?

[agneszitte]

What's the impact of setting material last (other than working around the issue)?

cc @kazo0, @Xiaoy312

[Xiaoy312]

dont we always initialize XamlControlRsources first?
the obviously impact is the default control styles, since the last initialized library will contribute first
also didnt we went over this last time, and there are problem no matter which gets initialized last? either fluent style or material style is broken depending on the order.

[kazo0]

Two paths:

1. Material -> Fluent and then we re-init Material in the MaterialContentPresenter for the SamplePageLayout here This is our current method
2. Fluent -> Material and then we re-init Fluent in the FluentContentPresenter for SamplePageLayout here

With Option 1 we are re-initializing the lesser of two evils since I would assume MaterialToolkitTheme is less heavy than XamlControlsResources (right?). Downside is we aren't using Material by default for the styling of the outer shell of the application, so we may run into issues similar to what we originally had if we were to start using CheckBoxes/RadioButtons/etc. outside of just the sample areas.

With Option 2 we are re-initializing XamlControlsResources, which is probably pretty large. Although, it would probably be re-initialized less often as Material is usually the default tab to be loaded when opening up sample pages (actually not sure if the resource would be loaded regardless or only if the contentpresenter's visibility changes to visible?). Upside is that Material is the default styling for the entire application in this case

After doing a quick test, the problem we are seeing here is avoided if we initialize Material last (Option 2)

Material on page load

If I switch to Fluent

I'm good with swapping the order but this still doesn't address why this isn't working specifically on mobile when you have a TemplateBound property that is set to an overridden ThemeResource