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
✨ Show label when live story is updated and user is on last page. #22700
Conversation
This pull request introduces 1 alert when merging e009887 into 7d9c822 - view on LGTM.com new alerts:
|
5b7af93
to
456dafc
Compare
Updated the PR with the most recent UX spec. PTAL. See previews below for reference: You'll notice that on the three panel view, the pagination button isn't updated when there is a new page. This is tracked here #22770 |
b8c5f1d
to
d7686c7
Compare
0af6d25
to
e2fc00d
Compare
Yep, it's the gif, sorry. Here is a screenshot with a better resolution of how it actually looks. You can see that the font is already bold. I corrected the opacity of the outer circle to the spec and now it's clearer that there are two circles. I also added a border radius for the box edges but I will increase it to make it look more like the mocks since I didn't get an exact number. Also added a bit more space on the right. |
Could you please post a screenshot of that UI when displayed RTL? The last
margin you added might break that display :(
On Mon, Jun 10, 2019 at 5:37 PM Enrique Marroquin ***@***.***> wrote:
Can't tell if it's just because of the low fidelity of the GIF, but it
looks like there's only one circle and not two?
Yep, it's the gif, sorry. Here is a screenshot with a better resolution of
how it actually looks. You can see that the font is already bold.
I corrected the opacity of the outer circle to the spec and now it's
clearer that there are two circles. I also added a border radius for the
box edges but I will increase it to make it look more like the mocks since
I didn't get an exact number.
Also added a bit more space on the right.
[image: image]
<https://user-images.githubusercontent.com/5449100/59228523-0ec2f300-8ba6-11e9-80c3-dc992943cfef.png>
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#22700?email_source=notifications&email_token=AALMITDZH6UCF3XFO2ENJQLPZ3CRLA5CNFSM4HUBN3KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLJ5FI#issuecomment-500604565>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALMITGEHY45TRXV7FRLDXDPZ3CRLANCNFSM4HUBN3KA>
.
--
Gabriel Majoulet | UX Engineer | gmajoulet@google.com
|
if (!this.isBuilt_) { | ||
return; | ||
} | ||
this.vsync_.mutate(() => { | ||
this.getShadowRoot().setAttribute(MESSAGE_DISPLAY_CLASS, 'noshow'); | ||
this.getShadowRoot().setAttribute(message, 'noshow'); |
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.
Sorry I know this is the type of thing that's very difficult to test (manually, or in any automated fashion), but how do multiple messages override each other? Does the first one just disgust completely once the second one comes in?
I suspect that would be the case, but I'm not actually sure whether that's okay? This can result in weird edge cases when one message is triggered right after another. It's probably fine if it's two audio message since they'd both come from user interactions, but if it's an audio message followed by a live list update, the user won't have had time to read the audio message.
Should we consider queuing the messages like toast frameworks (likely) would?
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.
I tested it and right now they are both shown, and eventually disappear. Since this seems to be a very specific edge case, do you mind if I address it in a follow-up?
I filed #22778 to keep track.
|
||
.i-amphtml-story-has-new-page-circle-icon { | ||
background: rgba(3, 255, 160, 1) !important; | ||
border-radius: 50% !important; |
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.
This should have a 4px
border at rgba(3, 255, 160, 0.5)
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.
Did you mean to comment this on the line below of the box-shadow, which represents the outer circle?
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.
If so, according to the spec the outer circle is supposed to be 10px in width, while the inner circle is 6px in width.
And if I understand correctly, the box-shadow spread
property specifies the radius of the circle. Meaning that if we want a 10px-wide circle, then the want to have a 5px radius. And since the inner circle is a 6px-wide circle (with a radius of 3px), then the box-shadow spread
property should be 2px to add up to a total radius of 5px, giving us a 10px-wide outer circle.
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.
This is ready for another review 👍 |
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.
Would be good to add a visual test for this; could come as a separate PR
Sounds good, will do in a follow up PR. Thanks both! |
…pproject#22700) * show label when story is updated and user is on last page. * better translation label & use same timeoutid. * revised position and style of label according to newest UX spec. * add more space on the right of the text and increase border radius. * fix padding and circle color values. * fix rtl, add i-amphtml prefix * fix css
Follow up for #22519
Partial for #21714
Shows a label when a live story is updated with new pages and the user is on the last page.
Preview:
EDIT: updated UX