-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add announcement area for new features #1561
Conversation
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 PR isn't reviewable as there's no companion PR in the L10N repo to check against, so all the strings are ???
(However, it looks like the React PR has all the strings in the pendingTranslations.ftl
file.
Added two CSS notes!
static/scss/components/whatsnew.scss
Outdated
display: initial; | ||
} | ||
|
||
button { |
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: this should be broken out into its own class/section: .c-whatsnew-entry-content
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.
static/scss/components/whatsnew.scss
Outdated
&:hover { | ||
background-color: $color-blue-50; | ||
color: $color-white; | ||
} |
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.
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.
l10n PR wasn't submitted yet (the strings in the React PR were tentative) because the content wasn't final yet, but it has now been submitted! mozilla-l10n/fx-private-relay-l10n#63 |
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 did a round of just running/testing and did some quick design comparisons with the Figma layout. There are a a few major things missing, LMK if any of these were omitted intentionally (since we have the new front-end coming soon).
UX:
- History/News toggle state
- Close/cancel button in top right corner
- Clear all button in bottom right corner
UI Differences:
- Border in between two news items (and in the history/news toggle header)
- Padding for elements inside the feed panel
- Note: It's 13px/6px for non-hovered/hovered states, so I would put a
$spacing-sm
on both the parent and child elements in the feed.
- Note: It's 13px/6px for non-hovered/hovered states, so I would put a
- The hover color is wrong (but you're using the correct color (
$color-violet-05
). Can you confirm that the variables are actually overwriting the Protocol tokens? - Missing triangle bubble on top of news feed
- The number (encased in yellow circle) is in italics
- Additional horizontal padding on "News" item when on hover/active (at least left side, maybe both?)
Will do a deeper dive / code review tomorrow!
@maxxcrawford Yes, see my initial PR description :)
Tony and Eduardo were OK with this approach. I've omitted the close button as well since there's no header now, and it can also be closed by clicking outside of the menu. As for the remaining issues:
So I investigated this, and it looks like @import "libs/protocol/css/components/forms/choice.scss"; in Removing that import from
I tried fixing this, but the horizontal padding on the other menu items is a lot smaller, so if I were to make space for this, the "News" entry would look very out-of-place. I'm also a bit afraid to touch this, since the menu items are already a bit inconsistent between the Premium and Free themes, and so I'm not sure what I'd break if I were to start messing with those spacings. So I propose accepting the smaller padding for now. Kooha-02-25-2022-09-53-41.mp4 |
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.
A couple things, I can't seem to close the tab when clicking the news button again.
https://user-images.githubusercontent.com/13066134/156044262-c05fdbda-f307-4420-ae94-cd3ba2f1d379.mov
Another thing is that when I shrink the device width, the panel gets cut off at a certain breakpoint (around 762px). Are we keeping the whats new feature on mobile as well?
https://user-images.githubusercontent.com/13066134/156044637-352b3131-0126-4fa5-82e1-38f8a1748bb3.mov
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.
Nice fixups. I had a ton of nits, and I appreciate you knocking them out.
I found one non-blocking CSS issue. I'm approving, but please be sure to check out @codemist's comments above. Thanks!
li { | ||
display: none; | ||
padding: $spacing-sm 0; | ||
border-bottom: 1px solid $color-light-gray-30; |
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.
Quick note: We're at "code freeze" today, so I'm going to merge this (after I fix the analytics conflict) and let you do a follow up PR for the other issues (including what I called out"). |
…a for new features
New feature description
This adds a menu that highlights new features. Note that this is slightly limited compared to the acceptance criteria: since only a few entries are shown at this time, the menu shows the entire history. I've prepared a separate PR to implement the full feature set in React, which will be used by the time there are more entries: #1562.
Screenshot (if applicable)
Kooha-02-21-2022-16-39-31.mp4
How to test
Checklist
/static/scss/libs/protocol/css/includes/tokens/dist/index.scss
).