Fixes #8002

Background

The dismissAfterConfirm flag will determine if the dialog will be dismissed after the confirm action is clicked. Its default behavior is to dismiss after confirm since the existing implementations utilize this.

This change is being made because the username changer will need to show a confirmation & progress dialog and the result of the associated operations will determine if the dialog should be dismissed or not.

Main Changes

The builder now has a parameter for the flag, and this is how the functionality is initiated.

 new FullScreenDialogFragment.Builder(getContext())
                .setTitle(R.string.username_changer_title)
                .setAction(R.string.username_changer_action)
                .setOnConfirmListener(this)
                .setOnDismissListener(this)
                .setDismissAferConfirm(false) // this is the flag.
                .setContent(UsernameChangerFullScreenDialogFragment.class, bundle)
                .build(); 

Testing

1. Use the same methods described in the WP Android block of the abstract username fragment PR description to access the suggestions screen easily.

2. Simply modify the builder that's used to launch the dialog in the SignUpEpilogueFragment with the dismissAfterConfirm flag similar to the example above.

The result of this will be that clicking the Save action will do nothing.
Notice in the example below that the ripple effect signifying the click is shown on the Save action but no dismissal occurs.

Left - Default behaviour. Right - Dismiss disabled.
( Sorry for the differences in screen size. Utilized two different devices when testing 😅)

Update release notes:

• If there are user facing changes, I have added an item to RELEASE-NOTES.txt.