Bug 39239 - Xamarin.Forms.Platform.Android.FontExtensions.ToScaledPixel missing case for NamedSize.Default
Summary: Xamarin.Forms.Platform.Android.FontExtensions.ToScaledPixel missing case for ...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.5.2
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-03-01 06:54 UTC by David
Modified: 2016-04-25 16:52 UTC (History)
2 users (show)

Tags: ac
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 FIXED

Description David 2016-03-01 06:54:36 UTC
The Xamarin.Forms.Platform.Android.FontExtensions.ToScaledPixel extension method is missing the case for NamedSize.Default. A case for NamedSize.Default should be added as returning 14.

Use case exhibiting bug:

In Forms code:
Font font = Font.SystemFontOfSize(NamedSize.Default).WithAttributes(FontAttributes.Bold);

Pass it into custom renderer, then:
float textSizeSp = font.ToScaledPx();

It will return a value of 0 instead of 14, because there is no case statement for NamedSize.Default.
Comment 1 Jason Smith [MSFT] 2016-03-10 19:09:05 UTC
Should be fixed in 2.2.0-pre1
Comment 2 Parmendra Kumar 2016-04-25 16:52:49 UTC
To verify this issue I have tried to reproduce this issue and not able to reproduce this issue.

Could you please provide me sample test case? so that I can verify this issue efficiently. 

Thanks.