Bug 60953 - Style size not honored after FontAttributes set
Summary: Style size not honored after FontAttributes set
Status: RESOLVED DUPLICATE of bug 60883
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.5.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-12-02 15:50 UTC by Edward Brey
Modified: 2017-12-03 15:06 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 60883

Description Edward Brey 2017-12-02 15:50:30 UTC
If you set a Label to have a Style that sets the text size, and also set FontAttributes in a Span for the label's FormattedText, the Style's text size is ignored for that span.

var label = new Label { Style = Device.Styles.ListItemDetailTextStyle };
var text = new FormattedString();
text.Spans.Add(new Span { FontAttributes = FontAttributes.Italic, Text = "Too big" });
text.Spans.Add(new Span { Text = "Just right" });
label.FormattedText = text;
Comment 1 Paul DiPietro [MSFT] 2017-12-03 15:06:50 UTC
Sounds like 60883 which also mentions some FontAttribute issues.

*** This bug has been marked as a duplicate of bug 60883 ***