Platforms Impacted

• iOS
• visionOS
• macOS

Description of changes

If the root view of the bottom sheet had a non-zero frame origin, the offset of the sheet would be miscalculated because the offset function was using the view frame and not the view bounds. When calculating the offset, we should use the view bounds so that the offset is calculated relative to the bottom sheet's root view's own space.

Binary change

(how is our binary size impacted -- see https://github.com/microsoft/fluentui-apple/wiki/Size-Comparison)

Verification

In the BottomSheetControllerDemo, I validated that the bottom sheet is correctly laid out when the bottom sheet view has an offset applied to its top anchor.

Visual Verification

In the first row of images, you can see in the before that the sheet in the collapsed state is not visible and in the after it is. In the second row, you can see in the before that the sheet is push way off the screen due to the calculation using the frame and not the bounds, and in the after you can see that it is correctly positioned.

Before	After

Pull request checklist

This PR has considered:

• Light and Dark appearances
• iOS supported versions (all major versions greater than or equal current target deployment version)
• VoiceOver and Keyboard Accessibility
• Internationalization and Right to Left layouts
• Different resolutions (1x, 2x, 3x)
• Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
• iPad Pointer interaction
• SwiftUI consumption (validation or new demo scenarios needed)
• Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow