-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IconSources don't respect Style values #2568
Comments
It's odd too that these two scenarios produce different results because of this: <AutoSuggestBox QueryIcon="Setting" Margin="0,0,0,16"/>
<AutoSuggestBox>
<AutoSuggestBox.QueryIcon>
<IconSourceElement>
<SymbolIconSource Symbol="Setting"/>
</IconSourceElement>
</AutoSuggestBox.QueryIcon>
</AutoSuggestBox> So even those these both end up as |
Ref microsoft/microsoft-ui-xaml#2568 Also added WPF TryFindResource method to LogicalTree helpers - thanks for review/assist @rudyhuyn
@StephenLPeters @michael-hawker There also is the MUXC FontIconSource, which seems to respect the property properly as it passes all properties down to the generated FontIcon. This issue however is about the WUXC FontIconSource. Does it make sense to keep this issue open as with WinUI 3, those would be unified, and then we would use the MUXC FIS which works correctly? |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I just realized that I can't style an Icon/IconSource, when I get the
FontIconSource
from the developer's XAML it's fixed at20
forFontSize
, any amount of style I have in my template is ignored and won't inherit or override that FontSize value, even if I callClearValue
on the FontIcon, as that just sets it back to 20...For instance if I have the following XAML:
The TextBlock value respects the parent FontSize value (set or from style), but the IconSourceElement does not, event though I didn't specify a
FontSize
property in the resource (if I did, I'd expect it to use that like other style/override scenarios).Originally posted by @michael-hawker in #1494 (comment)
The text was updated successfully, but these errors were encountered: