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.

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

LockScreen bounds should always be full bounds of Main screen #1499

Conversation

justingluck93
Copy link
Contributor

@justingluck93 justingluck93 commented Dec 10, 2019

Fixes #1492

This PR is ready for review.

Risk

This PR makes no API changes.

Testing Plan

  • I have verified that I have not introduced new warnings in this PR (or explain why below)
  • [n/a] I have run the unit tests with this PR
  • I have tested this PR against Core and verified behavior (if applicable, if not applicable, explain why below).

Unit Tests

There are no unit tests for this class

Core Tests

Tested against TDK

Summary

Made the lockscreen always be the full size of the phone screen when presented

Bug Fixes

Fixes the issue that sets the lockscreen to the size of the appWindow, in some cases the appWIndow may not be the full size of the screen. This can cause issues with how the lockscreen looks when presented.

CLA

@justingluck93 justingluck93 added the bug A defect in the library label Dec 10, 2019
@justingluck93 justingluck93 self-assigned this Dec 10, 2019
@joeljfischer
Copy link
Contributor

Waiting for issue reporter

@joeljfischer joeljfischer changed the title LockScreen bounds should always been full bounds of Main screen LockScreen bounds should always be full bounds of Main screen Dec 12, 2019
@joeljfischer
Copy link
Contributor

Closed in favor of #1509

@joeljfischer joeljfischer deleted the bugfix/issue-1492-SDLLockScreenViewController-abnormalUI branch January 2, 2020 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect in the library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants