Bug 51152 - Specifying ContentPage.Padding breaks Windows Phone
Summary: Specifying ContentPage.Padding breaks Windows Phone
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: unspecified
Hardware: Other Other
: Normal normal
Target Milestone: ---
Assignee: E.Z. Hart [MSFT]
Depends on:
Reported: 2016-12-29 21:09 UTC by Chris Hand
Modified: 2017-06-19 23:29 UTC (History)
3 users (show)

Tags: uwp
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 Chris Hand 2016-12-29 21:09:24 UTC
This Xaml worked on Android, iPhone emulator, and UWP. When run as a Windows Phone 8.1 App on a nokia 521, none of the controls were displayed. Removeing the ContentPage.Padding tag allowed the controls to appear. Also tried specifying the WinPhone property using values "0,0,0,0" and "1,1,1,1". Neither approach worked.

    <OnPlatform x:TypeArguments="Thickness" iOS="0,20,0,0"/>
    <Label Text = "What is your name?"/>
    <Entry Placeholder ="Name" />
    <Label Text = "What is your phone number?"/>
    <Entry Placeholder ="PhoneNumber" Keyboard="Telephone" />
Comment 1 E.Z. Hart [MSFT] 2017-02-15 03:06:00 UTC
(In reply to Chris Hand from comment #0)

Which version of Xamarin.Forms are you seeing this behavior on?
Comment 2 E.Z. Hart [MSFT] 2017-06-19 23:29:01 UTC
Because we have not received a reply to our request for more information we are
closing this issue. If you are still encountering this issue, please reopen the
ticket with the requested information. Thanks!