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
New design for PM and stream recipient bars. #23782
Conversation
Ignore the CI failures for now. Once the design is finalized, I can easily take care of it now. |
It's cool being able to play around with this! Here are the issues I spotted... |
|
I noticed some awkward behaviors at the top of the message feed:
|
586e037
to
af4b250
Compare
Updated the PR to fix the 1st bug you noticed. |
Huh, maybe a zoom issue? |
Good progress. I see the horizontal spacing is a bit different. It just feels that there is too much space for the icon: For some reason switching the theme makes headers stuck in the previous theme. But reloading the page resolves that: About the background color of the PMs. Let's reevaluate that once we can see messages on the proper dark background instead of this bright blue. @alya I highly recommend to have dark theme background change together (close) to merging that |
I'm not sure the color collation is correct for some cases. For example if I take hashtag icon color from this (# 9cbcda): |
af4b250
to
b3b675d
Compare
@terpimost addressed all your concerns. Please review again! |
b3b675d
to
ad46016
Compare
wow, didn't realize this is difficult to rebase now. |
Yeah, it is not ready for review due to rebase conflicts, I am working on it right now, I have to basically rewrite the whole PR. |
ad46016
to
463349f
Compare
@terpimost this should be ready for another review now. |
stream_privacy template has conditions to show stream privacy icon for all the cases, so we use it here since we also want to show `#` icon for public streams.
@@ -78,6 +80,7 @@ export function switch_to_dark_theme() { | |||
command: "/night", | |||
on_success(data) { | |||
dark_theme.enable(); | |||
message_lists.update_recipient_bar_background_color(); |
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.
These slash commands shouldn't be doing UI updates at all, should they? I would expect the server_events
system to be responsible for them.
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.
My guess is we have dark_theme.enable();
here so that user feels that the color change to dark theme was quick. Since, dark_theme.enable();
is here, I need to do message_lists.update_recipient_bar_background_color();
here as well.
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.
OK; I suppose we can add a comment. In any case, we could look at making dark_theme.enable
call message_lists.update_recipient_bar_background_color
as a follow-up I suppose.
Following important changes are being made here: * color_class lib is removed since it not used anywhere now. * We don't need the `dark_background` class since the background color is already adjusted based on color scheme. So, all instances of it being used is removed.
c4e16e7
to
04faeae
Compare
This mostly includes the CSS changes for recipient row design, most of the HTML and JS changes are present in previous commits to this.
This commit doesn't modify the lock and hashtag icon in settings.
04faeae
to
debe2d5
Compare
This looks great, tagging to merge once CI passes; I'll deploy (#23782 (comment) seems pretty minor as a code cleanup/comment tweak, so let's leave that for a follow-up -- given it's not a functional change and is mostly a preexisting detail I noticed, there's no reason to block on it.) |
Do we need an issue for updating the stream privacy icon (i.e. the last commit work) for the settings pages? Could make sense for @sahil839 to take over that portion of it. |
I will just open a PR for it, it seems like a simple delete. |
It’s unused since commit 7e47300 (zulip#23782). Signed-off-by: Anders Kaseorg <anders@zulip.com>
It’s unused since commit 7e47300 (zulip#23782). Signed-off-by: Anders Kaseorg <anders@zulip.com>
It’s unused since commit 7e47300 (zulip#23782). Signed-off-by: Anders Kaseorg <anders@zulip.com>
It’s unused since commit 7e47300 (zulip#23782). Signed-off-by: Anders Kaseorg <anders@zulip.com>
This PR is aimed towards making significant progress in the direction of #22021.
Figma design was a great source used for finalizing some of the details on space between elements in this PR.
The changes that are mentioned in the issue but are not included in the PR are: