MAGE-323: safe zone handling

[amber-klaviyo]

Description

add safe zone to user provided offsets

Due Diligence

• I have tested this on a simulator or a physical device.
• I have added sufficient unit/integration tests of my changes.
• I have adjusted or added new test cases to team test docs, if applicable.
• I am confident these changes are compatible with all iOS and XCode versions the SDK currently supports.

Release/Versioning Considerations

• Patch Contains internal changes or backwards-compatible bug fixes.
• Minor Contains changes to the public API.
• Major Contains breaking changes.
• Contains readme or migration guide changes.
  • If so, please merge to a feature branch so documentation updates only go live upon official release.
• This is planned work for an upcoming release.
  • If no, author or reviewer should account for this in a release plan, or describe why not below.

Changelog / Code Overview

Test Plan

Related Issues/Tickets

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 965b8ce. Configure here.}

[cursor]

Negative dimensions when margins exceed screen size

Medium Severity

availableWidth and availableHeight can become negative when the combined safe area insets and user-provided margins exceed the screen dimensions. Since clampedWidth and clampedHeight are computed via min(width, availableWidth), they inherit this negative value, resulting in a CGRect with negative dimensions. This could happen on smaller devices in landscape (where safe area left/right insets are significant) or with large user-configured margins. The values need to be floored at zero.

 

^{Reviewed by Cursor Bugbot for commit 965b8ce. Configure here.}