WordPress-iOS
WordPress-iOS copied to clipboard
[Notification Refresh] Replace the old Comment Detail header with the new Content Preview component
Fixes https://github.com/Automattic/wordpress-mobile/issues/29
Post Preview | Comment Preview | Comment Preview without avatar |
---|---|---|
Test Instructions
Post Reply Notification
- Run Jetpack and login
- Navigate to the Notifications screen
- Find a Post Reply notification and click it
- The header should be the same as the design
- Click on the header, it should keep the original behavior
Comment Reply Notification
- Run Jetpack and login
- Navigate to the Notifications screen
- Find a Comment Reply notification and click it
- The header should be the same as the design
- Click on the header, it should keep the original behavior
Regression Notes
-
Potential unintended areas of impact The behavior when the header is tapped should be maintained.
-
What I did to test those areas of impact (or what existing automated tests I relied on) Manual testing
-
What automated tests I added (or what prevented me from doing so) None.
PR submission checklist:
- [x] I have completed the Regression Notes.
- [x] I have considered adding unit tests for my changes.
- [x] I have considered adding accessibility improvements for my changes.
- [x] I have considered if this change warrants user-facing release notes and have added them to
RELEASE-NOTES.txt
if necessary.
Testing checklist:
- [x] WordPress.com sites and self-hosted Jetpack sites.
- [x] Portrait and landscape orientations.
- [x] Light and dark modes.
- [x] Fonts: Larger, smaller and bold text.
- [x] High contrast.
- [x] VoiceOver.
- [x] Languages with large words or with letters/accents not frequently used in English.
- [x] Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
- [x] iPhone and iPad.
- [x] Multi-tasking: Split view and Slide over. (iPad)
📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
App Name | ![]() |
|
Configuration | Release-Alpha | |
Build Number | pr23083-e8a5b25 | |
Version | 24.7 | |
Bundle ID | org.wordpress.alpha | |
Commit | e8a5b251b7fd5bd7f02c5d3a94ed6e22b781300c | |
App Center Build | WPiOS - One-Offs #9713 |
📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
App Name | ![]() |
|
Configuration | Release-Alpha | |
Build Number | pr23083-e8a5b25 | |
Version | 24.7 | |
Bundle ID | com.jetpack.alpha | |
Commit | e8a5b251b7fd5bd7f02c5d3a94ed6e22b781300c | |
App Center Build | jetpack-installable-builds #8757 |
There is a case when a comment is opened by
ReaderCommentsViewController
on top ofCommentDetailViewController
.
This behavior was developed in the 1st phase where we redirect the user directly to Reader Comments screen if they don't permission to moderate the comment.
Also based on the View Debugger screenshot you shared, the Reader Comments screen is a child of NotificafionCommentDetailViewController
, not CommentDetailViewController
, which are 2 different view controllers.
As for old header design in the Reader Comments, I intentionally avoided redesigning it because I think it's out of scope of this phase. 🤔
This behavior was developed in the 1st phase where we redirect the user directly to Reader Comments screen if they don't permission to moderate the comment.
Yeah, totally understand it, but the screen looks like a notification detail and does even have navigation buttons on the toolbar. That's why it looks confusing and not organically within the brand-new design system. 🤔