Bug 28988 - NamedSize enumeration does not return a larger value between a 7" and 10" tablet.
Summary: NamedSize enumeration does not return a larger value between a 7" and 10" tab...
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.4.1
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-04-10 13:26 UTC by Jon Douglas [MSFT]
Modified: 2016-08-09 13:48 UTC (History)
1 user (show)

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:

Description Jon Douglas [MSFT] 2015-04-10 13:26:56 UTC

Using the NamedSize enumeration for a FontSize, android tablets do not seem to adhere to a "Larger" size based on the tablet size. Given a 7" tablet, the NamedSize.Large returns a value of 21.78. Given a 10" tablet, the NamedSize.Large returns a value of 22. This font value does not seem to fit a larger device such as a 10" tablet.

*Expected Behavior

NamedSize should return a larger font value calculated by the device's height/width.


Xamarin Forms Labs currently implements a FontManager that uses a DisplayManager service to get the height/width to scale a font.


Comment 1 Rui Marinho 2016-08-09 13:48:59 UTC
Old Bug We Think is Now Invalid

Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.

For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d Warm regards, Xamarin Forms Team