Password field show/hide icon does not update according to theme

[Pallav-sculptsoft]

The password field's show/hide icon does not automatically update when the app theme changes (e.g., between light and dark themes). When switching themes, the icon remains unchanged, which affects the UI consistency.

Steps to Reproduce:

1. Add a TextFieldPasswordShowHideAttachment to the TextField control for the password field, as shown below:

<material:TextField Title="Password" IsPassword="True">
    <material:TextField.Attachments>
        <material:TextFieldPasswordShowHideAttachment />
    </material:TextField.Attachments>
</material:TextField>

2. Run the application with any theme, such as light.

3. Change the theme to dark and observe the password field's show/hide icon.

Expected Behavior:
The show/hide icon should automatically update to match the current theme (light or dark).

Actual Behavior:
The icon does not change when the theme is switched, causing inconsistency with the application's overall theme.

Proposed Solution:
Consider using an extension method, SetAppTheme, on the icon to ensure it updates based on the current theme. This would enable the icon to match the theme dynamically.

[Pallav-sculptsoft]

This will may help...

 private Path GetPathFromData(Geometry data)
    {
        var path = new Path
        {
            VerticalOptions = LayoutOptions.Center,
            Data = data,
        };

        // Set the Fill color based on the current theme
        path.SetAppThemeColor(Path.FillProperty,
            light: ColorResource.GetColor("OnBackground").WithAlpha(0.5f),
            dark: ColorResource.GetColor("OnBackgroundDark").WithAlpha(0.5f));

        return path;
    }

[enisn]

Thanks for showing the workaround @Pallav-sculptsoft

I got the issue, it is initialized with the current theme colors for better performance at the first. I can update it to use AppThemeBinding

[Pallav-sculptsoft]

Thanks @enisn, Great to hear! Thanks for the response.

Could you please share the estimated timeline for this update and the targeted release version? This will help us plan accordingly.