Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
There is a requirement to be able to define a Style with a FontSize that will obey accessibility changes on iOS (presumably, whatever the equivalent on Android is also).
The current support that is close to this (basing a style on an existing dynamic style) does not let you specify/change the default FontSize for that style and therefore does not fulfill this requirement.
**Steps to Reproduce:**
<Style x:Key="CustomStyle" TargetType="Label" BaseResourceKey="SubtitleStyle">
<Setter Property="Label.FontSize" Value="8"/>
<Setter Property="Label.TextColor" Value="Color.Pink"/>
The FontSize always stays at 8, regardless of accessibility changes.
FontSize should start at 8 when on "default" accessibility and then obey any changes.
**Build Date & Platform:**
I misunderstood how this worked on iOS. I did not realize that the font sizes being used are inherited from the OS, using UIFont.Preferred*. Changing the FontSize in a Style would already override that.
On iOS, to manually handle font size changes when accessibility changes, you can listen for the "UIContentSizeCategoryDidChangeNotification" which is fired when accessibility changes. This might also be required if using a non-system font (custom fonts). This is probably not a bug and it's already implemented as the OS supports - someone from the Forms team, please confirm.
Correct this is not a bug, cheers :)