The sample app does not include any considerations for TVs with overscan.
TV Safe Area:
https://docs.microsoft.com/en-us/windows/uwp/design/devices/designing-for-tv#tv-safe-area
Steps to reproduce the behavior:
The sample app should pad interactive content as indicated in the docs:
If applicable, add screenshots to help explain your problem.
NuGet Package(s):
Package Version(s):
Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [X] May 2019 Update (18362)
- [ ] Insider Build (build number: )
App min and target version:
- [ ] Fall Creators Update (16299)
- [X] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] Insider Build (xxxxx)
Device form factor:
- [ ] Desktop
- [X] Xbox
- [ ] Surface Hub
- [ ] IoT
Visual Studio
- [ ] 2017 (version: )
- [X] 2019 (version: )
- [ ] 2019 Preview (version: )
Add any other context about the problem here.
Hello shweaver-MSFT, 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 馃檶
Inspiration: https://github.com/shweaver-MSFT/TVSafePanel
Thanks @shweaver-MSFT! I could see a nifty MarkupExtension that returns a Thickness value for this being handy to use on any sort of UIElement. 馃檪