This PR is related to issue#21189.
This issue shows a problem that 'There's no visual confirmation when clicking UNDO button to restore the blog previously blocked'.
Here's the issue video:
Simply add a toast message on the screen may not have impact on other areas which I have not confirmed yet. I'll keep looking for influence caused by my changes and work on to solve it if necessary!
What I did to test those areas of impact (or what existing automated tests I relied on)
Still need to do.
What automated tests I added (or what prevented me from doing so)
Still need to do.
PR Submission Checklist:
[x] I have completed the Regression Notes.
[x] I have considered adding accessibility improvements for my changes.
[ ] I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.
Testing Checklist (strike-out the not-applying and unnecessary ones):
[ ] WordPress.com sites and self-hosted Jetpack sites.
[ ] Portrait and landscape orientations.
[ ] Light and dark modes.
[ ] Fonts: Larger, smaller and bold text.
[ ] High contrast.
[ ] Talkback.
[ ] Languages with large words or with letters/accents not frequently used in English.
[ ] Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
[ ] Large and small screen sizes. (Tablet and smaller phones)
[ ] Multi-tasking: Split screen and Pop-up view. (Android 10 or higher)
Fixes #
Description:
This PR is related to issue#21189. This issue shows a problem that 'There's no visual confirmation when clicking UNDO button to restore the blog previously blocked'. Here's the issue video:
https://github.com/user-attachments/assets/f8b1dd31-a89d-4964-ad90-fe584117f7e5
Solutions:
1.Add a toast message on the screen when clicking the UNDO button by snackbayMessage: 2.Add a new toast message into strings.xml:
Result:
https://github.com/user-attachments/assets/04de8579-a02d-4b43-bd6f-1b5de08b1d2e
To Test:
Regression Notes
Potential unintended areas of impact
Simply add a toast message on the screen may not have impact on other areas which I have not confirmed yet. I'll keep looking for influence caused by my changes and work on to solve it if necessary!
What I did to test those areas of impact (or what existing automated tests I relied on)
Still need to do.
What automated tests I added (or what prevented me from doing so)
Still need to do.
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):