Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/web/templates/topic_sidebar_actions.hbs

133 lines
5.8 KiB
Handlebars
Raw Normal View History

Add chevron menu for topics in left sidebar. The first menu option supported is to narrow to the topic. The chevron only shows up if you turn on feature_flags.muting. (imported from commit 17482f538a6d3e4ff96a36c042bad972d34f4b11)
2013-09-17 23:04:44 +02:00
<ul class="nav nav-list topics_popover">
topic-popover: Change design of topic popover. Extracts the topic name from the list items and display it in the popover title. Add a seperator between normal user and admin only options.
2020-05-15 16:08:25 +02:00
<li>
<p class="topic-name">
topic-popover: Add chevron-right icon in topic popover title.
2020-06-20 17:50:19 +02:00
<i class="fa fa-chevron-right" aria-hidden="true" style="color: {{color}}"></i>
topic-popover: Change design of topic popover. Extracts the topic name from the list items and display it in the popover title. Add a seperator between normal user and admin only options.
2020-05-15 16:08:25 +02:00
<b>{{topic_name}}</b>
</p>
</li>
templates: Mark all void tags as self-closing. This reverses the policy that was set, but incompletely enforced, by commit 951514dd7dd2fafb67e9e9c6930d31b9295741c0. The self-closing tag syntax is clearer, more consistent, simpler to parse, compatible with XML, preferred by Prettier, and (most importantly now) required by FormatJS. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-04-21 00:46:14 +02:00
<hr />
topic-popover: Change design of topic popover. Extracts the topic name from the list items and display it in the popover title. Add a seperator between normal user and admin only options.
2020-05-15 16:08:25 +02:00
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
{{#if development}}
<li class="hidden-for-spectators">
<div class="tabs-container">
topic_popover: Update 'data-tippy-content' and 'aria-label'. Update the 'data-tippy-content' and 'aria-label' from * 'Mute topic' to 'Mute' * 'Unmute topic' to 'Unmute' * 'Follow topic' to 'Follow' in the left-sidebar topic-popover UI to toggle visibility policies. As we plan to add a 'Default' option, 'Default topic' doesn't sound good (if we stay consistent with the earlier texts). Instead, 'Mute', 'Default', 'Unmute', and 'Follow' sound good, and it is obvious that we are performing action on the topic itself (as it is a topic popover). There is no need to add an extra 'topic' keyword.
2023-08-15 08:59:46 +02:00
<div class="tab-option tippy-zulip-tooltip {{#if (eq visibility_policy all_visibility_policies.MUTED)}}selected-tab{{/if}}" data-visibility-policy="{{all_visibility_policies.MUTED}}" data-tippy-content="{{t 'Mute' }}" aria-label="{{t 'Mute' }}">
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
<i class="zulip-icon zulip-icon-mute-new"></i>
</div>
topic_popover: Add a 'Default' option and Show 'Unmute' conditionally. The 'Unmute' option is available in not-muted streams only when it is the current value. Add a 'Default' option. Available in both muted and not-muted streams. 'Default' corresponds to the 'INHERIT' visibility policy. Summary: * In muted streams:   Four options: Mute, Default, Unmute, and Follow. * In not-muted streams:   Three options: Mute, Default, and Follow.   The fourth option, 'Unmute' is available only when it is the   current value. Reason for conditional availability of 'Unmute' option: In a not-muted stream, 'Unmute' has no special significance. We only show 'Default' because both 'Default' and 'Unmute' has the same behaviour in the not-muted stream. This avoids the big design downside of showing this fourth nearly-identical option to users who are just in the normal default state of a normal topic within a normal stream We only show the 'Unmute' option in the not-muted stream to users. if they have followed a sequence of steps that led them to 'Unmute' state in a not-muted stream.  For example: Mute a stream > Unmute a topic > Unmute the stream By doing so, we avoid destroying information. The user, when mutes the stream again, the topic will retain the 'Unmute' state. New icons for Mute, Default, Unmute, and Follow.
2023-08-10 10:04:26 +02:00
<div class="tab-option tippy-zulip-tooltip {{#if (eq visibility_policy all_visibility_policies.INHERIT)}}selected-tab{{/if}}" data-visibility-policy="{{all_visibility_policies.INHERIT}}" data-tippy-content="{{t 'Default' }}" aria-label="{{t 'Default' }}">
<i class="zulip-icon zulip-icon-inherit"></i>
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
</div>
topic_popover: Add a 'Default' option and Show 'Unmute' conditionally. The 'Unmute' option is available in not-muted streams only when it is the current value. Add a 'Default' option. Available in both muted and not-muted streams. 'Default' corresponds to the 'INHERIT' visibility policy. Summary: * In muted streams:   Four options: Mute, Default, Unmute, and Follow. * In not-muted streams:   Three options: Mute, Default, and Follow.   The fourth option, 'Unmute' is available only when it is the   current value. Reason for conditional availability of 'Unmute' option: In a not-muted stream, 'Unmute' has no special significance. We only show 'Default' because both 'Default' and 'Unmute' has the same behaviour in the not-muted stream. This avoids the big design downside of showing this fourth nearly-identical option to users who are just in the normal default state of a normal topic within a normal stream We only show the 'Unmute' option in the not-muted stream to users. if they have followed a sequence of steps that led them to 'Unmute' state in a not-muted stream.  For example: Mute a stream > Unmute a topic > Unmute the stream By doing so, we avoid destroying information. The user, when mutes the stream again, the topic will retain the 'Unmute' state. New icons for Mute, Default, Unmute, and Follow.
2023-08-10 10:04:26 +02:00
{{#if (or stream_muted topic_unmuted)}}
<div class="tab-option tippy-zulip-tooltip {{#if (eq visibility_policy all_visibility_policies.UNMUTED)}}selected-tab{{/if}}" data-visibility-policy="{{all_visibility_policies.UNMUTED}}" data-tippy-content="{{t 'Unmute' }}" aria-label="{{t 'Unmute' }}">
<i class="zulip-icon zulip-icon-unmute-new"></i>
</div>
{{/if}}
topic_popover: Update 'data-tippy-content' and 'aria-label'. Update the 'data-tippy-content' and 'aria-label' from * 'Mute topic' to 'Mute' * 'Unmute topic' to 'Unmute' * 'Follow topic' to 'Follow' in the left-sidebar topic-popover UI to toggle visibility policies. As we plan to add a 'Default' option, 'Default topic' doesn't sound good (if we stay consistent with the earlier texts). Instead, 'Mute', 'Default', 'Unmute', and 'Follow' sound good, and it is obvious that we are performing action on the topic itself (as it is a topic popover). There is no need to add an extra 'topic' keyword.
2023-08-15 08:59:46 +02:00
<div class="tab-option tippy-zulip-tooltip {{#if (eq visibility_policy all_visibility_policies.FOLLOWED)}}selected-tab{{/if}}" data-visibility-policy="{{all_visibility_policies.FOLLOWED}}" data-tippy-content="{{t 'Follow' }}" aria-label="{{t 'Follow' }}">
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
<i class="zulip-icon zulip-icon-follow"></i>
</div>
</div>
</li>
<hr/>
{{else}}
{{#if stream_muted}}
{{#unless topic_unmuted}}
<li class="hidden-for-spectators">
<a tabindex="0" class="sidebar-popover-unmute-topic" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="zulip-icon zulip-icon-unmute" aria-hidden="true"></i>
{{t "Unmute topic"}}
</a>
</li>
{{else}}
<li class="hidden-for-spectators">
<a tabindex="0" class="sidebar-popover-remove-unmute" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="zulip-icon zulip-icon-mute" aria-hidden="true"></i>
{{t "Mute topic"}}
</a>
</li>
{{/unless}}
topic_sidebar_actions: Implement new mute/unmute toggle UI for topics. For topics in muted streams, replace the "Mute topic" option in the three-dot topic menu with an "Unmute topic" option, which should make the topic unmuted. For unmuted topics in muted streams, show the regular "Mute topic" option, which should specifically mark the topic as muted, as usual. Also, used new unmute icon for unmute option in three-dot menu for topics in muted stream. Fixes part of #24243
2023-04-11 21:51:38 +02:00
{{else}}
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
{{#unless topic_muted}}
topic_sidebar_actions: Implement new mute/unmute toggle UI for topics. For topics in muted streams, replace the "Mute topic" option in the three-dot topic menu with an "Unmute topic" option, which should make the topic unmuted. For unmuted topics in muted streams, show the regular "Mute topic" option, which should specifically mark the topic as muted, as usual. Also, used new unmute icon for unmute option in three-dot menu for topics in muted stream. Fixes part of #24243
2023-04-11 21:51:38 +02:00
<li class="hidden-for-spectators">
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
<a tabindex="0" class="sidebar-popover-mute-topic" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
popovers: Tweak mute/unmute icons for topic menu. While we use a different convention in recent conversations and recipient bars, in this context, it make sense for this icon to just match the action we'll be doing.
2023-04-26 03:00:10 +02:00
<i class="zulip-icon zulip-icon-mute" aria-hidden="true"></i>
topic_sidebar_actions: Implement new mute/unmute toggle UI for topics. For topics in muted streams, replace the "Mute topic" option in the three-dot topic menu with an "Unmute topic" option, which should make the topic unmuted. For unmuted topics in muted streams, show the regular "Mute topic" option, which should specifically mark the topic as muted, as usual. Also, used new unmute icon for unmute option in three-dot menu for topics in muted stream. Fixes part of #24243
2023-04-11 21:51:38 +02:00
{{t "Mute topic"}}
</a>
</li>
topic_popover: Add support to follow a topic from the topic_popover. This commit adds support for following a topic from the topic three-dot menu in the left sidebar. Three options, i.e., 'Mute topic', 'Unmute topic', and 'Follow topic', are shown at the top of the menu (in the mentioned order), regardless of whether the stream is muted or unmuted. We can no longer set the topic's visibility_policy to INHERIT (the default value) from this menu. The changes are visible in the development environment only. Fixes #25917. Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com> Co-authored-by: Hardik Dharmani <Ddharmani99@gmail.com>
2023-06-14 11:41:48 +02:00
{{else}}
<li class="hidden-for-spectators">
<a tabindex="0" class="sidebar-popover-remove-mute" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="zulip-icon zulip-icon-unmute" aria-hidden="true"></i>
{{t "Unmute topic"}}
</a>
</li>
{{/unless}}
{{/if}}
topic_sidebar_actions: Implement new mute/unmute toggle UI for topics. For topics in muted streams, replace the "Mute topic" option in the three-dot topic menu with an "Unmute topic" option, which should make the topic unmuted. For unmuted topics in muted streams, show the regular "Mute topic" option, which should specifically mark the topic as muted, as usual. Also, used new unmute icon for unmute option in three-dot menu for topics in muted stream. Fixes part of #24243
2023-04-11 21:51:38 +02:00
{{/if}}
left sidebar: Add support to unstar all messages in topic. This adds support for unstarring all (starred) messages from a particular topic, from the topic popover. The earlier implementation of this in #16898 was reverted in bc55aa6a01641e81b2e380127ff109cf92e18618 (#17429) because it had two problems- 1. The crash reported in bc55aa6a01641e81b2e380127ff109cf92e18618 was due to message_store returning undefined. This happens when the message itself hasn't been fetched from the server yet, but we know that the message is starred from the ids in `page_params` in `starred_messages.js`. This commit handles this case explicitly. Note that, we simply ignore those messages which we haven't fetched, and because of this, it may happen that we don't unstar some messages from that topic. The correct implementation for this would be to ask the backend for starred IDs in a topic. 2. The earlier implementation actually unstarred **all** messages. This was because it grabbed the topic and stream_id from the topic popover `data` attributes, after the topic popover had been closed. This passed `undefined`, which the function then interpreted as an action to unstar all messages. With this commit, we use the confirm_dialog widget, which eliminates the need to store this data in the DOM.
2021-03-08 09:25:25 +01:00
{{#if has_starred_messages}}
popovers: Hide most irrelevant options for spectators. This simplifies the UI for these popovers to not have tons of options that cannot be accessed.
2021-09-20 08:23:25 +02:00
<li class="hidden-for-spectators">
js: Add tabindex attribute for anchor tag to allow focus. This adds tabindex='0' in anchor tags for allowing the message menu popover box to be focusable using hotkey 'i' through keyboard. This is a necessary follow up to 729c09074a52677dbea9e8cdaf1f69f40b048e69, which removed the href attribute from anchor tags to which click-handlers were attached, which resulted in making them non-focusable as jQuery doesn't allow anchor tags to be focusable without tab-index or href attribute. Fixes #21125.
2022-02-14 21:34:58 +01:00
<a tabindex="0" class="sidebar-popover-unstar-all-in-topic" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
left sidebar: Add support to unstar all messages in topic. This adds support for unstarring all (starred) messages from a particular topic, from the topic popover. The earlier implementation of this in #16898 was reverted in bc55aa6a01641e81b2e380127ff109cf92e18618 (#17429) because it had two problems- 1. The crash reported in bc55aa6a01641e81b2e380127ff109cf92e18618 was due to message_store returning undefined. This happens when the message itself hasn't been fetched from the server yet, but we know that the message is starred from the ids in `page_params` in `starred_messages.js`. This commit handles this case explicitly. Note that, we simply ignore those messages which we haven't fetched, and because of this, it may happen that we don't unstar some messages from that topic. The correct implementation for this would be to ask the backend for starred IDs in a topic. 2. The earlier implementation actually unstarred **all** messages. This was because it grabbed the topic and stream_id from the topic popover `data` attributes, after the topic popover had been closed. This passed `undefined`, which the function then interpreted as an action to unstar all messages. With this commit, we use the confirm_dialog widget, which eliminates the need to store this data in the DOM.
2021-03-08 09:25:25 +01:00
<i class="fa fa-star-o" aria-hidden="true"></i>
templates: Replace unnecessary {{#tr}} blocks with {{t}} helper. `{{#tr}}` supports HTML and allows translators to accidentally introduce HTML, so it’s safer to use the `{{t}}` helper unless HTML is needed. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2023-03-15 23:51:27 +01:00
{{t "Unstar all messages in topic" }}
left sidebar: Add support to unstar all messages in topic. This adds support for unstarring all (starred) messages from a particular topic, from the topic popover. The earlier implementation of this in #16898 was reverted in bc55aa6a01641e81b2e380127ff109cf92e18618 (#17429) because it had two problems- 1. The crash reported in bc55aa6a01641e81b2e380127ff109cf92e18618 was due to message_store returning undefined. This happens when the message itself hasn't been fetched from the server yet, but we know that the message is starred from the ids in `page_params` in `starred_messages.js`. This commit handles this case explicitly. Note that, we simply ignore those messages which we haven't fetched, and because of this, it may happen that we don't unstar some messages from that topic. The correct implementation for this would be to ask the backend for starred IDs in a topic. 2. The earlier implementation actually unstarred **all** messages. This was because it grabbed the topic and stream_id from the topic popover `data` attributes, after the topic popover had been closed. This passed `undefined`, which the function then interpreted as an action to unstar all messages. With this commit, we use the confirm_dialog widget, which eliminates the need to store this data in the DOM.
2021-03-08 09:25:25 +01:00
</a>
</li>
{{/if}}
popovers: Hide most irrelevant options for spectators. This simplifies the UI for these popovers to not have tons of options that cannot be accessed.
2021-09-20 08:23:25 +02:00
<li class="hidden-for-spectators">
popovers: Add keyboard support for topic popovers in left sidebar. This commit adds arrow, vim_up/vim_down and enter hotkey support for navigating the popover menu.
2020-07-09 03:18:27 +02:00
<a tabindex="0" class="sidebar-popover-mark-topic-read" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
topic_sidebar_actions.handlebars: Upgrade font-awesome icon style.
2017-06-08 07:09:57 +02:00
<i class="fa fa-book" aria-hidden="true"></i>
topic-popover: Change design of topic popover. Extracts the topic name from the list items and display it in the popover title. Add a seperator between normal user and admin only options.
2020-05-15 16:08:25 +02:00
{{t "Mark all messages as read"}}
Clean topic_sidebar_actions handlebar to use 4 space indents.
2017-02-15 21:11:59 +01:00
</a>
topic_sidebar: Add support to copy topic link to clipboard. This commits adds the support to copy a topic link to the clipboard by introducing a new "Copy link to topic" topic sidebar action which is placed below the "Mark all messages as read" action. Basically, this does the same job as right clicking upon the topic name and selecting "Copy link". Closes #18946
2021-06-24 09:26:39 +02:00
</li>
<li>
popovers: Migrate the topic_menu popover to Tippy. This commit migrates the topic_menu popover from stream_popover.js to popover_menus.js. Since the data required for rendering is large, it has been moved inside popover_menus_data.js to improve code readability. Getting the link of the topic for the clipboardJS inside the onMount instance was not working with the existing method. To make it easier to work with, a new attribute, data-clipboard-text, is added to the 'Copy link to topic' anchor tag. This allows the clipboardJS to catch the URL. The value of data-clipboard-text is sent from popover_menus.js to the topic_sidebar_actions template. Fixes: #23891
2023-03-30 16:17:14 +02:00
<a tabindex="0" class="sidebar-popover-copy-link-to-topic" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}" data-clipboard-text="{{ url }}">
topic_sidebar: Add support to copy topic link to clipboard. This commits adds the support to copy a topic link to the clipboard by introducing a new "Copy link to topic" topic sidebar action which is placed below the "Mark all messages as read" action. Basically, this does the same job as right clicking upon the topic name and selecting "Copy link". Closes #18946
2021-06-24 09:26:39 +02:00
<i class="fa fa-link" aria-hidden="true"></i>
{{t "Copy link to topic"}}
</a>
Clean topic_sidebar_actions handlebar to use 4 space indents.
2017-02-15 21:11:59 +01:00
</li>
Add feature to mark all in stream/topic as read with mouse. Fixes #736.
2016-05-08 15:20:51 +02:00
popovers: Display move topic option to all users with permission. Previously, the "Move topic" option was only displayed to organization administrators, despite the new setting making who can move topics between streams configurable. Making this migration requires us to remove the text on the previous "Admin actions" divider, and just make it an hrule, to avoid confusing normal users, while still providing a hint that moving topics is a non-personal operation. We also change the ordering for consistency.
2021-05-13 18:17:57 +02:00
{{#if can_move_topic}}
<hr />
topic-popover: Change design of topic popover. Extracts the topic name from the list items and display it in the popover title. Add a seperator between normal user and admin only options.
2020-05-15 16:08:25 +02:00
messages: Add support for quickly deleting all messages in a topic. This is primarily a feature for onboarding, where an organization administrator might send a bunch of random test messages as part of joining, but then want a pristine organization when their users later join. But it can theoretically be used for other use cases (e.g. for moderation or removing threads that are problematic in some way). Tweaked by tabbott to handle corner cases with is_history_public_to_subscribers. Fixes #10912.
2019-01-18 17:40:54 +01:00
<li>
popovers: Display move topic option to all users with permission. Previously, the "Move topic" option was only displayed to organization administrators, despite the new setting making who can move topics between streams configurable. Making this migration requires us to remove the text on the previous "Admin actions" divider, and just make it an hrule, to avoid confusing normal users, while still providing a hint that moving topics is a non-personal operation. We also change the ordering for consistency.
2021-05-13 18:17:57 +02:00
<a tabindex="0" class="sidebar-popover-move-topic-messages" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="fa fa-arrows" aria-hidden="true"></i>
{{t "Move topic"}}
messages: Add support for quickly deleting all messages in a topic. This is primarily a feature for onboarding, where an organization administrator might send a bunch of random test messages as part of joining, but then want a pristine organization when their users later join. But it can theoretically be used for other use cases (e.g. for moderation or removing threads that are problematic in some way). Tweaked by tabbott to handle corner cases with is_history_public_to_subscribers. Fixes #10912.
2019-01-18 17:40:54 +01:00
</a>
</li>
stream_popover: Add "Rename topic" option in topic sidebar popover. This commit adds "Rename topic" option in topic sidebar popover which will be shown when user is only allowed to edit topics and not streams. Note that we still cannot show or hide the option as per the time limit setting (since client may not have the first message of the topic locally), so we just show or hide it as per move_messages_within_stream_policy setting. Fixes #19886.
2023-04-14 18:58:10 +02:00
{{else if can_rename_topic}}
<hr />
<li>
<a tabindex="0" class="sidebar-popover-rename-topic-messages" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="fa fa-pencil" aria-hidden="true"></i>
{{t "Rename topic"}}
</a>
</li>
{{/if}}
popovers: Fix showing resolve topic option in sidebar popover. We previously showed "Mark as unresolved" or "Mark as resolved" option in topic sidebar popover only is user was allowed to move messages between streams. This commit fixes it to show if user is allow to move within stream, or in other words edit the topic, since resolving or unresolving topics is essentially topic ediitng only. Note that we still cannot show or hide the option as per the time limit setting (since client may not have the first message of the topic locally), so we just show or hide it as per move_messages_within_stream_policy setting.
2023-04-17 09:13:56 +02:00
{{#if can_rename_topic}}
left sidebar: Implement basic resolve topic option. Fixes part of #18751.
2021-06-11 20:50:03 +02:00
<li>
<a tabindex="0" class="sidebar-popover-toggle-resolved" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="fa fa-check" aria-hidden="true"></i>
{{# if topic_is_resolved }}
{{t "Mark as unresolved"}}
{{else}}
{{t "Mark as resolved"}}
{{/if}}
</a>
</li>
messages: Add support for quickly deleting all messages in a topic. This is primarily a feature for onboarding, where an organization administrator might send a bunch of random test messages as part of joining, but then want a pristine organization when their users later join. But it can theoretically be used for other use cases (e.g. for moderation or removing threads that are problematic in some way). Tweaked by tabbott to handle corner cases with is_history_public_to_subscribers. Fixes #10912.
2019-01-18 17:40:54 +01:00
{{/if}}
Add mute/unmute to topic sidebar menu (imported from commit 96abc03e840ed6d720da8355f29242d9a070563e)
2013-09-18 00:29:42 +02:00
stream_data: Rename sub.is_admin to sub.is_realm_admin. This commit renames sub.is_admin to sub.is_realm_admin such that we can clearly differentiate between realm and stream admins.
2020-08-15 21:04:05 +02:00
{{#if is_realm_admin}}
messages: Allow moving a topic to another stream. This completes the implementation of support for moving a topic to another stream by adding a basic UI for it. Fixes #6427, which was previously the most-upvoted issue request in Zulip. There are likely to be a bunch of follow-up UI improvements on top of this change to fully flesh out the feature.
2020-02-19 01:38:34 +01:00
<li>
popovers: Display move topic option to all users with permission. Previously, the "Move topic" option was only displayed to organization administrators, despite the new setting making who can move topics between streams configurable. Making this migration requires us to remove the text on the previous "Admin actions" divider, and just make it an hrule, to avoid confusing normal users, while still providing a hint that moving topics is a non-personal operation. We also change the ordering for consistency.
2021-05-13 18:17:57 +02:00
<a tabindex="0" class="sidebar-popover-delete-topic-messages" data-stream-id="{{ stream_id }}" data-topic-name="{{ topic_name }}">
<i class="fa fa-trash" aria-hidden="true"></i>
{{t "Delete topic"}}
messages: Allow moving a topic to another stream. This completes the implementation of support for moving a topic to another stream by adding a basic UI for it. Fixes #6427, which was previously the most-upvoted issue request in Zulip. There are likely to be a bunch of follow-up UI improvements on top of this change to fully flesh out the feature.
2020-02-19 01:38:34 +01:00
</a>
</li>
{{/if}}
Add chevron menu for topics in left sidebar. The first menu option supported is to narrow to the topic. The chevron only shows up if you turn on feature_flags.muting. (imported from commit 17482f538a6d3e4ff96a36c042bad972d34f4b11)
2013-09-17 23:04:44 +02:00
</ul>