Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Style does not applies to UWP Xamarin.forms Entry element #5678

Closed
MetropolisCZ opened this issue Aug 12, 2021 · 42 comments
Closed

Style does not applies to UWP Xamarin.forms Entry element #5678

MetropolisCZ opened this issue Aug 12, 2021 · 42 comments
Labels
area-External Not owned by the WinUI team, not actionable in this repository.

Comments

@MetropolisCZ
Copy link

MetropolisCZ commented Aug 12, 2021 •
edited
Loading

Hi, I have this issue: When I create Xamarin.Forms app and add Entry there, it is not styled by your library.

Describe the bug
Style does not applies to UWP Xamarin.forms Entry element

Steps to reproduce the bug
Create any Xamarin.Forms app, where you will add Entry element. Add Microsoft.UI.Xaml library (with NuGet) and --> Entry´s style is still 'Windows 10'

Expected Behavior
To look like this :)
image
(from https://docs.microsoft.com/en-us/windows/apps/get-started/build-apps-for-windows)

Screenshots

image
Buttons look new, but Entry still old

Version Info

NuGet package version:

Microsoft.UI.Xaml 2.6.1

Windows app type:

UWP Win32
Yes
Windows version Saw the problem?
Insider Build (22000.120) Yes
Device form factor Saw the problem?
Desktop Yes

Sorry if the issue is stupid :)
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Aug 12, 2021
@StephenLPeters
Copy link
Contributor

Unfortunately I don't know the mechanism that Xamarin Forms apps are intended to receive the WinUI Styles, if they are at all. I think this would be better to ask in the Xamarin Forms Github

@StephenLPeters StephenLPeters added area-External Not owned by the WinUI team, not actionable in this repository. and removed needs-triage Issue needs to be triaged by the area owners labels Aug 12, 2021
@ghost
Copy link

ghost commented Aug 17, 2021

🎉This issue was addressed in #5432, which has now been successfully released as Microsoft.UI.Xaml v2.7.0-prerelease.210816001.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 19, 2021

🎉This issue was addressed in #5531, which has now been successfully released as Microsoft.UI.Xaml v2.6.2-prerelease.210818003.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 20, 2021

🎉This issue was addressed in #5628, which has now been successfully released as Microsoft.UI.Xaml v2.6.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 20, 2021

🎉This issue was addressed in #5472, which has now been successfully released as Microsoft.UI.Xaml v2.6.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 20, 2021

🎉This issue was addressed in #5447, which has now been successfully released as Microsoft.UI.Xaml v2.6.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 20, 2021

🎉This issue was addressed in #5432, which has now been successfully released as Microsoft.UI.Xaml v2.6.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 20, 2021

🎉This issue was addressed in #5359, which has now been successfully released as Microsoft.UI.Xaml v2.6.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 19, 2022

🎉This issue was addressed in #5779, which has now been successfully released as Microsoft.UI.Xaml vMicrosoft.Experimental.UI.Xaml.2.8.0-prerelease.220118001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5870, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5930, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5910, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #6004, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5968, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #6138, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5779, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5870, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5930, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5973, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5910, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #6004, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5968, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #6142, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #6138, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5779, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5870, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5930, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5973, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5910, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #6004, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5968, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #6142, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #6138, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5779, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Aug 31, 2022

🎉This issue was addressed in #7197, which has now been successfully released as Microsoft.UI.Xaml v2.8.2-prerelease.220830001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5870, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5930, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5910, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #6004, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5968, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #6138, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5779, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-External Not owned by the WinUI team, not actionable in this repository.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@StephenLPeters @MetropolisCZ