Adjust safe area insets strategy for 26

[mickael-menu]

Fixed

Navigator

• The safe area insets strategy was adjusted to take into account changes in iOS/iPadOS 26.

[Copilot]

Pull Request Overview

This PR adjusts the safe area insets strategy to accommodate changes in iOS/iPadOS 26. The change replaces a custom notchAreaInsets implementation with direct use of the window's safeAreaInsets property.

Key changes:

• Removes the custom notchAreaInsets computed property and its complex logic for handling device notches and status bars
• Replaces all usages of notchAreaInsets with window?.safeAreaInsets across PDF and EPUB view implementations
• Updates comments to reflect the simplified approach of using window safe area insets directly

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
UIView.swift	Removes the custom notchAreaInsets computed property that handled device-specific safe area calculations
PDFDocumentView.swift	Replaces notchAreaInsets usage with direct window safe area insets for content inset calculations
EPUBReflowableSpreadView.swift	Updates content inset logic to use window safe area insets instead of custom notch area calculations
EPUBFixedSpreadView.swift	Switches from custom notch area insets to window safe area insets for bounds calculations
CHANGELOG.md	Documents the safe area insets strategy adjustment for iOS/iPadOS 26 compatibility

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}