-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
message_list: Add buttons for different actions. #32091
base: main
Are you sure you want to change the base?
Conversation
I didn't spend a lot of time trying to find edge cases since we are still in the trial phase, so think of it this PR as prototype worth deploying to test out the feature. |
Hello @zulip/design members, this pull request was labeled with the "UI experiment" label, so you may want to check it out! |
6ba6aea
to
e6bc2bb
Compare
Nice! I wonder if a shorter tooltip delay would be better, since the buttons are unlabeled now (maybe LONG rather than EXTRA_LONG). |
It's definitely much more subtle than the previous version. I'd like to see this on CZO! |
@@ -544,7 +545,7 @@ export function process_unread_messages_event({ | |||
!message_lists.current.can_mark_messages_read() && | |||
message_lists.current.has_unread_messages() | |||
) { | |||
unread_ui.notify_messages_remain_unread(); | |||
message_list_navigation.update(); |
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 refactor to have a message_list_navigation.update
function has appeared in both versions of this; if we keep doing iterations on this, maybe we make a prep commit we can merge to reduce overall churn.
@@ -221,7 +222,7 @@ export function initialize_kitchen_sink_stuff() { | |||
if (delta < 0 && message_viewport.at_rendered_top()) { | |||
navigate.up(); | |||
} else if (delta > 0 && message_viewport.at_rendered_bottom()) { | |||
navigate.down(); | |||
navigate.down(false, 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.
It might be nice to pass these two options by name rather than positional values.
e6bc2bb
to
f661bcc
Compare
f661bcc
to
1636cf8
Compare
1636cf8
to
af69642
Compare
Updated to move navigation buttons to the right. |
af69642
to
3f1048d
Compare
3f1048d
to
baa5c5e
Compare
baa5c5e
to
30efbef
Compare
30efbef
to
61d7b7d
Compare
Deploying back on chat.zulip.org again. |
61d7b7d
to
930f4c4
Compare
Pushed to resolve conflicts. |
border-radius: 5px; | ||
} | ||
|
||
.message-list-navigation-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.
A good refactor that this makes me think of is extracting a message_feed.css
with some of the outer containing classes like div.message-list
, .empty_feed_notice
, .sub-unsub-message
, .date_row
, etc.
This CSS would belong there; would be helpful for the goal of shrinking zulip.css
. Not a blocker for this, but maybe a fine project if you're in the mood for that style of work.
web/templates/tooltip_templates.hbs
Outdated
@@ -107,14 +107,14 @@ | |||
</div> | |||
</template> | |||
<template id="all-message-tooltip-template"> | |||
<div class="views-tooltip-container" data-view-code="all_messages"> |
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.
Could this data-view-code
refactor be put in a prep commit or PR? I'm not sure what it's about, but it seems like it could be done earlier to help simplify 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.
Opened #32728
web/src/tippyjs.ts
Outdated
trigger: "mouseenter", | ||
delay: EXTRA_LONG_HOVER_DELAY, | ||
appendTo: () => document.body, | ||
}); |
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 think these can be declared in message_list_navigation.ts
; generally it's nicer to have all the code for a feature in one place, and so I've been trying to avoid just having every tooltip go in here when it could just live in its own module.
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.
Sure, moved!
@@ -880,6 +877,7 @@ export function fast_track_current_msg_list_to_anchor(anchor: string): void { | |||
return msg_list_data.first()!.id; | |||
}, | |||
}); | |||
message_lists.current.unfocus_navigation_bar(); |
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'm not sure I understand some of these changes in when we do the checks for updating these.
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.
Yeah, we can make the focus / unfocus logic simple in the codebase but we need to nail down the experience we want here too.
930f4c4
to
7bfb085
Compare
Pushed mainly to just resolve conflicts. Didn't address any feedback in the design thread yet since the discussion didn't seem to have reached a conclusion. |
7bfb085
to
7535898
Compare
7535898
to
da7912c
Compare
Fixes #30405
Fixes #18728
Updated this based on discussion in https://chat.zulip.org/#narrow/stream/101-design/topic/Add.20navigation.20buttons.20below.20messages.20.2330405