Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Reader] Increase Reader comments like count disabled state alpha #20445

Conversation

RenanLukas
Copy link
Contributor

@RenanLukas RenanLukas commented Mar 11, 2024

Fixes #20443

Important

I'm concerned that the opacity for disabled state is too close to the enabled state, but if the opacity is lower than that it might not seem that the the like count is disabled (cc @osullivanchris in case you have any ideas). Do not merge until we have confirmation that this works from a design perspective.


To Test:

  1. Install Jetpack and sign in with a self-hosted site.
  2. Open Reader.
  3. Select "Discover" feed.
  4. Open any post with comments.
  5. 🔍 Open the comments list screen: the number of likes label and icon (e.g. 2 likes) should be visible.

Before (like count with state disabled)

before_light_Screenshot 2024-03-11 at 4 23 54 PM before_dark_Screenshot 2024-03-11 at 4 23 44 PM

After (like count with state disabled)

after_light_Screenshot 2024-03-11 at 4 20 22 PM after_dark_Screenshot 2024-03-11 at 4 20 30 PM

Like count with state enabled (just for reference since there were no changes targeting this state)

Screenshot 2024-03-11 at 4 54 02 PM Screenshot 2024-03-11 at 4 54 15 PM


Regression Notes

  1. Potential unintended areas of impact

    • None
  2. What I did to test those areas of impact (or what existing automated tests I relied on)

    • Manual testing
  3. What automated tests I added (or what prevented me from doing so)

    --


PR Submission Checklist:

  • I have completed the Regression Notes.
  • 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)

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Mar 11, 2024

Jetpack📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack Jetpack
FlavorJalapeno
Build TypeDebug
Versionpr20445-2168f10
Commit2168f10
Direct Downloadjetpack-prototype-build-pr20445-2168f10.apk
Note: Google Login is not supported on these builds.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Mar 11, 2024

WordPress📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress WordPress
FlavorJalapeno
Build TypeDebug
Versionpr20445-2168f10
Commit2168f10
Direct Downloadwordpress-prototype-build-pr20445-2168f10.apk
Note: Google Login is not supported on these builds.

Copy link
Contributor

@thomashorta thomashorta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me, I just added a small suggestion to make things consistent with Material values.

Even though I kinda agree that disabled and medium emphasis look a bit similar, they are consistent with the system and Material values, and they do look different enough, in my opinion.

Comment on lines 5 to 6
<item android:alpha="@dimen/reader_comments_like_count_disabled_alpha" android:color="?attr/colorOnSurface" android:state_enabled="false" android:state_selected="false" />
<item android:alpha="@dimen/reader_comments_like_count_disabled_alpha" android:color="?attr/colorOnSurface" android:state_enabled="false" android:state_selected="true" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Suggestion: since we are already using the emphasis medium alpha from the material lib (line 8) why don't we also use the emphasis disabled alpha for this one, which is material_emphasis_disabled and has value 0.38.

That's the one used by default in material component texts and outlines so I think it would make sense to use that, and it's pretty close to what you're proposing here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, thanks! ✅

@RenanLukas RenanLukas added the Do Not Merge In PRs with this label, our automation will fail a require check, preventing accidental merging label Mar 11, 2024
Copy link

sonarcloud bot commented Mar 11, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

@osullivanchris osullivanchris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in the future work I'm doing for comments, I'm separating the like count from the like action, as we do for posts. So this will be different then. Maybe not worth optimising the current one too much?

Screenshot 2024-03-12 at 17 05 49

@RenanLukas
Copy link
Contributor Author

RenanLukas commented Mar 12, 2024

Thanks for the review, @osullivanchris

Maybe not worth optimising the current one too much?

Makes sense 👍 (cc @develric since you reported the issue)

@RenanLukas RenanLukas removed the Do Not Merge In PRs with this label, our automation will fail a require check, preventing accidental merging label Mar 13, 2024
Copy link
Contributor

@develric develric left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the ping @RenanLukas 🙇 . What Chris says makes sense 👍 . I just gave it a quick test after the changes requested from Thomas and it's looking good, also code LGTM as well. I think it's a nice interim improvement :shipit:

Side note: comment improvements look really nice (the sample screen shared but also some neat early-stage brainstorming ideas on the topic I happened to see). Cannot wait for us to contribute to it ❤️

@RenanLukas RenanLukas merged commit ba91e0f into trunk Mar 13, 2024
20 of 24 checks passed
@RenanLukas RenanLukas deleted the issue/20443-comments-like-count-not-clearly-visible-with-ui-disabled branch March 13, 2024 16:07
@RenanLukas RenanLukas added this to the 24.5 milestone Mar 13, 2024
@RenanLukas RenanLukas self-assigned this Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Reader] Comments like count not clearly visible when UI is disabled
5 participants