Ios Ignore Safe Area
Using .ignoresSafeArea() on text labels, buttons, or any interactive element causes content to be clipped under the Dynamic Island, status bar notch, or home indicator on modern iPhones.
$ aoe install @community/anti-pattern-ios-ignore-safe-areaProjection
Always in _index.xml · the agent never has to ask for this.
IosIgnoreSafeArea [anti-pattern] v1.0.0
Using .ignoresSafeArea() on text labels, buttons, or any interactive element causes content to be clipped under the Dynamic Island, status bar notch, or home indicator on modern iPhones.
Loaded when retrieval picks the atom as adjacent / supporting.
IosIgnoreSafeArea [anti-pattern] v1.0.0
Using .ignoresSafeArea() on text labels, buttons, or any interactive element causes content to be clipped under the Dynamic Island, status bar notch, or home indicator on modern iPhones.
Label
iOS Applying ignoresSafeArea() to Content Views
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
System chrome physically obscures content placed outside safe areas, making it unreachable or invisible. This is especially severe on iPhone 14/15/16 Pro models with the Dynamic Island, which sits higher than a standard notch. Apple HIG Rule 1.2 requires all interactive and readable content to stay within safe area boundaries.
Instead Do
Apply .ignoresSafeArea() only to background fills, full-bleed decorative images, or edge-extending visuals. Never apply it to text, buttons, or any interactive element. In SwiftUI, use .ignoresSafeArea(.container, edges: .bottom) specifically on a background Color/Image, not on a VStack or Group containing content.
Loaded when retrieval picks the atom as a focal / direct hit.
IosIgnoreSafeArea [anti-pattern] v1.0.0
Using .ignoresSafeArea() on text labels, buttons, or any interactive element causes content to be clipped under the Dynamic Island, status bar notch, or home indicator on modern iPhones.
Label
iOS Applying ignoresSafeArea() to Content Views
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
System chrome physically obscures content placed outside safe areas, making it unreachable or invisible. This is especially severe on iPhone 14/15/16 Pro models with the Dynamic Island, which sits higher than a standard notch. Apple HIG Rule 1.2 requires all interactive and readable content to stay within safe area boundaries.
Instead Do
Apply .ignoresSafeArea() only to background fills, full-bleed decorative images, or edge-extending visuals. Never apply it to text, buttons, or any interactive element. In SwiftUI, use .ignoresSafeArea(.container, edges: .bottom) specifically on a background Color/Image, not on a VStack or Group containing content.
Relations
related: [@community/rule-ios-safe-area-insets, @community/rule-ios-flexible-layout, @community/constraint-ios-touch-target-44pt]
Label
iOS Applying ignoresSafeArea() to Content Views
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
System chrome physically obscures content placed outside safe areas, making it unreachable or invisible. This is especially severe on iPhone 14/15/16 Pro models with the Dynamic Island, which sits higher than a standard notch. Apple HIG Rule 1.2 requires all interactive and readable content to stay within safe area boundaries.
Instead Do
Apply .ignoresSafeArea() only to background fills, full-bleed decorative images, or edge-extending visuals. Never apply it to text, buttons, or any interactive element. In SwiftUI, use .ignoresSafeArea(.container, edges: .bottom) specifically on a background Color/Image, not on a VStack or Group containing content.
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/anti-pattern-ios-ignore-safe-area/atom.yaml