-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Reader] Increase Reader
comments like count disabled state alpha
#20445
Conversation
📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
|
There was a problem hiding this 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.
<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" /> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, thanks! ✅
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review, @osullivanchris
Makes sense 👍 (cc @develric since you reported the issue) |
There was a problem hiding this 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
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 ❤️
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:
Before (like count with state disabled)
After (like count with state disabled)
Like count with state enabled (just for reference since there were no changes targeting this state)
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
--
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):