Introduce FluentNotificationTriggerModel for FluentNotifcation to rework the Bump animation#2245
Merged
nodes11 merged 4 commits intomicrosoft:mainfrom Feb 21, 2026
Merged
Conversation
…h FluentNotification
joannaquu
reviewed
Feb 20, 2026
Demos/FluentUIDemo_iOS/FluentUI.Demo/Demos/NotificationViewDemoController_SwiftUI.swift
Outdated
Show resolved
Hide resolved
joannaquu
approved these changes
Feb 20, 2026
joannaquu
reviewed
Feb 20, 2026
Demos/FluentUIDemo_iOS/FluentUI.Demo/Demos/NotificationViewDemoController_SwiftUI.swift
Outdated
Show resolved
Hide resolved
joannaquu
approved these changes
Feb 20, 2026
joannaquu
approved these changes
Feb 21, 2026
joannaquu
pushed a commit
to joannaquu/fluentui-apple
that referenced
this pull request
Feb 24, 2026
…ork the Bump animation (microsoft#2245) * Add FluentNotificationTriggerModel for easier client interactions with FluentNotification
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Platforms Impacted
Description of changes
This change introduces the
FluentNotificationTriggerModel, which simplifies client interactions withFluentNotification. Currently, most of the notification state is managed throughMSFNotificationStateImpl, but this is not publicly exposed on the notification. Instead of exposing theMSFNotificationStateImplproperty on the notification, we are introducing a new observable model that clients can easily interact with.The first use case for this new model is to expose the
bumpbehavior. Previously, this behavior was enabled through the state object. However, pure SwiftUI views did not have a straightforward way to trigger it. With this change, clients can now settriggerModel.shouldBump = true, and the notification view will respond accordingly.This change also adds an option
onDismissparameter to theFluentNotificationinit which will be passed along to the state property. This is purely for the convienece of apps that useFluentNotificationdirectly.Binary change
(how is our binary size impacted -- see https://github.com/microsoft/fluentui-apple/wiki/Size-Comparison)
Verification
Validated in internal use cases. Updated demo controllers. See demo videos below.
Visual Verification
Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-02-20.at.12.01.35.mov
Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-02-20.at.12.16.20.mov
Pull request checklist
This PR has considered:
Microsoft Reviewers: Open in CodeFlow