Bring back support for Dialogs over non-FragmentActivity host #27790
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.
Summary
This commit had earlier (intentionally) stopped supporting DialogModule over non-FragmentActivity hosts.
The change was done for a genuine reason, but unfortunately, we have a number of brownfield clients within Microsoft who are finding it hard to change their host host activities in time, due to various reasons. As we expect the transition to take a while (Another 6 months), we would like to put back the support for legacy FragmentManager in DialogModule.
This change is an essential revert of the above mentioned commit.
Changelog
Bring back the support for legacy FragmentManager in DialogModule. This is required for brownfield applications who don't have ReactActivity as the host.
[CATEGORY] [TYPE] - Message
Test Plan