[WPF/MapControl] MapControl is on top of every other control
When using MapControl I am unable to place any other controls in WPF on top of it. It seems to be on top of everything for some reason.
I've not seen a version where this is fixed.
Steps to Reproduce
Steps to reproduce the behavior:
- Go to Reproduction repo link
- Go to
Sourcefolder - Open
MapControlBug.slnsolution - In
MainWindow.xamlverify that the button with contentHellois rendered over theMapControlin the XAML previewer. - Run the application and verify that
MapControlis rendered on top of the aforementionedButton
Expected behavior
MapControl should respect z index of other controls
Screenshots
How it looks in the previewer:
How it looks when I run the app:

Environment
WPF, .Net Core 3.1, Windows 10. NuGet Package(s): Microsoft.Toolkit.Wpf.UI.Controls Package Version(s): Microsoft.Toolkit.Wpf.UI.Controls: 6.1.2
Project .NET Version:
- [ ] .NET Framework (version: )
- [ ] .NET Core 3
- [X] .NET Core 3.1
Windows 10 Build Number:
- 21390.1
Device form factor:
- [X] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT
Visual Studio
- [ ] 2017 (version: )
- [X] 2019 (version: )
Hello meJevin, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.
This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.
FYI @marb2000
I get the same issue with MediaPlayerElement . I assume it is the case for all UWP controls hosted on WPF? Is there any work around?
I believe this is a general airspace issues, I thought Winforms host behaved the same way? Not sure if there's anything to be done. Thought there was a note somewhere about this... @marb2000?
You are right @michael-hawker it looks like air-space issues.