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

163 lines
9.1 KiB
Handlebars
Raw Normal View History

settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
<form class="display-settings-form">
display_settings: Rename and update the 'language-time' section. Rename the 'language-time' title to 'General'. As the 'language-time' section no longer exists, replace the 'lang-time-settings' classname with the 'general-settings' classname in the 'settings_display.js' file. Updated the 'change-the-time-format.md' and 'change-your-language.md' documentation files to reflect these changes. To pass the puppeteer_test Replaced the 'lang-time-settings-status' classname to 'general-settings-status' inside 'settings.test.ts' file.
2023-03-04 14:49:02 +01:00
<div class="general-settings {{#if for_realm_settings}}settings-subsection-parent{{else}}subsection-parent{{/if}}">
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
<!-- this is inline block so that the alert notification can sit beside
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
it. If there's not an alert, don't make it inline-block.-->
settings: Use save discard widget for showing indicator. We use save discard widget to show saving/failed indicators in the user and realm-level display settings.
2021-09-27 12:59:09 +02:00
<div class="subsection-header inline-block">
display_settings: Rename and update the 'language-time' section. Rename the 'language-time' title to 'General'. As the 'language-time' section no longer exists, replace the 'lang-time-settings' classname with the 'general-settings' classname in the 'settings_display.js' file. Updated the 'change-the-time-format.md' and 'change-your-language.md' documentation files to reflect these changes. To pass the puppeteer_test Replaced the 'lang-time-settings-status' classname to 'general-settings-status' inside 'settings.test.ts' file.
2023-03-04 14:49:02 +01:00
<h3>{{t "General" }}</h3>
{{> settings_save_discard_widget section_name="general-settings" show_only_indicator=(not for_realm_settings) }}
settings: Use save discard widget for showing indicator. We use save discard widget to show saving/failed indicators in the user and realm-level display settings.
2021-09-27 12:59:09 +02:00
</div>
settings: Fix bug in "Default user settings" section. There was no heading for "Time format" setting in the "Default user settings" section and thus no save-discard widget to update the setting. This commit fixes the bug and changes the heading to be only "Time" since there is no realm-level default of language setting. This bug was introduced in adb612a0b48.
2021-11-09 12:36:40 +01:00
{{#unless for_realm_settings}}
gear_menu: Allow spectators to select their default language. Set the default_language as cookie and reload the page so that the spectator can immediately see the language change in effect. We can reload the page forcefully for spectators since there is no chance of any work being lost. It is possible that the spectator may lose the selected message on doing so. This requires a new dependency, to be able to set cookies from frontend JavaScript. Fixes #21961
2022-05-02 11:15:25 +02:00
{{> language_selection_widget
section_name="default_language_name"
setting_value=default_language_name
settings: Fix save-discard widget fo. The save-discard widget was not showing and hiding correctly for the "Automated messages and emails" section in organization settings panel. This was because the "proposed_val" was always being returned as "undefined" for language setting as "data-language-code", which is used to check the proposed value of setting, was not set after changes in 36475daba7b. This commit fixes it by passing language_code value to language_selection_widget and thus setting "data-language-code" attribute correctly. The changes in 36475daba7b removed language_code parameter from language_selection_widget as it was not passed in the template from "Display settings" section. So, this commit also passes the language_code parameter to language_selection_widget from "Display settings" section. This change sets the "data-language-code" attribute even when it is not being used there, to make sure there is no reference to undefined fields in language_selection_widget. Note that the above bug was reproducible only if you have not changed the language even once and are trying to change the other settings, as the data-language-code attribute was set after selecting a language from the modal, but it was not set initially after rendering the page.
2023-07-28 11:31:24 +02:00
section_title=settings_label.default_language_settings_label
language_code=default_language }}
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{/unless}}
Add option for setting timezone in user display settings.
2017-04-02 20:59:22 +02:00
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
<div class="input-group">
<label for="twenty_four_hour_time" class="dropdown-title">{{ settings_label.twenty_four_hour_time }}</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="twenty_four_hour_time" class="setting_twenty_four_hour_time prop-element settings_select bootstrap-focus-style" id="{{prefix}}twenty_four_hour_time" data-setting-widget-type="string">
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
{{#each twenty_four_hour_time_values}}
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
<option value='{{ this.value }}'>{{ this.description }}</option>
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
{{/each}}
</select>
Clean display-settings.handlebars to use 4 space indents.
2017-04-26 04:45:03 +02:00
</div>
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
<div class="input-group">
display_settings: Rename and reorder the theme dropdown menu. Rename 'Sync with computer' to 'Automatic (follows system settings)', 'Light Theme' to 'Light' and 'Dark Theme' to 'Dark', and rename the color scheme label to 'Theme'. Reorder the dropdown menu to have light theme before dark theme.
2023-03-04 13:43:50 +01:00
<label for="color_scheme" class="dropdown-title">{{t "Theme" }}</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="color_scheme" class="setting_color_scheme prop-element settings_select bootstrap-focus-style" id="{{prefix}}color_scheme" data-setting-widget-type="number">
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{> dropdown_options_widget option_values=color_scheme_values}}
</select>
</div>
display_settings: Rename 'Theme' section to 'Emoji'. Rename the 'Theme' section to 'Emoji'. Since there is no 'Theme' section anymore, replace the 'theme-settings' classname with 'emoji-display-settings' in the 'settings_display.js' file. The existing "Theme" selector dropdown is moved from the now the 'Emoji' section to the 'General' section.
2023-03-04 13:28:12 +01:00
</div>
<div class="emoji-display-settings {{#if for_realm_settings}}settings-subsection-parent{{else}}subsection-parent{{/if}}">
<div class="subsection-header">
<h3 class="light">{{t "Emoji" }}</h3>
{{> settings_save_discard_widget section_name="emoji-display-settings" show_only_indicator=(not for_realm_settings) }}
</div>
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
<div class="input-group">
<label class="emoji-theme title">{{t "Emoji theme" }}</label>
settings: Refactor code that handles radio type settings. This commit changes the settings code to consider the parent div of the radio inputs as prop-element and not individual input elements since all inputs are actually for a single setting. We still need to handle these settings as special cases at some places but that can also be fixed. As a result of this change, we can use ID to get setting name from the element in populate_data_for_request.
2022-09-30 16:24:36 +02:00
<div class="emojiset_choices grey-box prop-element" id="{{prefix}}emojiset" data-setting-widget-type="radio-group" data-setting-choice-type="string">
settings: Pass user settings using settings_object variable. Instead of passing user settings directly as user_settings variable to the settings templates, we pass them using settings_object variable. This change is important so that we can use the exisiting display_settings and notification_settings template for realm-level default settings by passing realm-level settings using settings_source variable.
2021-08-25 13:03:05 +02:00
{{#each settings_object.emojiset_choices}}
settings: Do not use bootstrap css in radio-type display settings. We rewrite the CSS rules, handled by bootstrap for the radio buttons in display settings (both user and realm-level defaults), to settings.css as we are in process of removing bootstrap. This commit adds a new class "display-settings-radio-choice-label" to radio label elements in the display settings and the bootstrap CSS rules along with existing CSS defined by us for radio-type display settings are added to this class. This change will help us in future where we may want to have reusable components (like settings_checkbox) for radio-type settings with visual preview. The line-height property added to input element by bootstrap is not added to settings.css since it is already added for all inputs in zulip.css.
2022-11-22 11:22:27 +01:00
<label class="display-settings-radio-choice-label">
settings: Refactor code that handles radio type settings. This commit changes the settings code to consider the parent div of the radio inputs as prop-element and not individual input elements since all inputs are actually for a single setting. We still need to handle these settings as special cases at some places but that can also be fixed. As a result of this change, we can use ID to get setting name from the element in populate_data_for_request.
2022-09-30 16:24:36 +02:00
<input type="radio" class="setting_emojiset_choice" name="emojiset" value="{{this.key}}"/>
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
<span>{{this.text}}</span>
<span class="right">
{{#if (eq this.key "text") }}
<div class="emoji_alt_code">&nbsp;:relaxed:</div>
{{else}}
<img class="emoji" src="/static/generated/emoji/images-{{this.key}}-64/1f642.png" />
<img class="emoji" src="/static/generated/emoji/images-{{this.key}}-64/1f44d.png" />
<img class="emoji" src="/static/generated/emoji/images-{{this.key}}-64/1f680.png" />
<img class="emoji" src="/static/generated/emoji/images-{{this.key}}-64/1f389.png" />
{{/if}}
</span>
settings: Explain that Google blob emojis are deprecated. Part of fixing #19371.
2022-05-19 21:37:54 +02:00
{{#if (eq this.key "google-blob")}}
<span>(<em>{{t "deprecated" }}</em>)</span>
{{> ../help_link_widget link="/help/emoji-and-emoticons#change-your-emoji-set" }}
{{/if}}
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
</label>
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
{{/each}}
settings: Change the control for selecting emojiset to radio group. Fixes: #7260.
2017-11-02 21:25:36 +01:00
</div>
display-settings: Move emoticons option after emoji style. This new position is clearer about its role.
2018-03-23 22:38:00 +01:00
</div>
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
{{> settings_checkbox
setting_name="translate_emoticons"
settings: Pass user settings using settings_object variable. Instead of passing user settings directly as user_settings variable to the settings templates, we pass them using settings_object variable. This change is important so that we can use the exisiting display_settings and notification_settings template for realm-level default settings by passing realm-level settings using settings_source variable.
2021-08-25 13:03:05 +02:00
is_checked=settings_object.translate_emoticons
settings: Add prefix to settings_checkbox references in display_settings. This commit adds prefix paramter with value "user_" to the settings_checkbox references in display_settings.hbs such that ids are unique when we use display_settings.hbs for realm-level settings UI.
2021-08-19 21:04:24 +02:00
label=settings_label.translate_emoticons
settings: link to list of emoticon translations. Under "Emoji" under "Preferences", we link to the rules explaining what emoticons exist, e.g., :) translates to 😄, etc. These docs: https://zulip.com/help/configure-emoticon-translations Fixes #18147.
2023-09-21 17:46:29 +02:00
help_link="/help/enable-emoticon-translations"
settings: Add prefix to settings_checkbox references in display_settings. This commit adds prefix paramter with value "user_" to the settings_checkbox references in display_settings.hbs such that ids are unique when we use display_settings.hbs for realm-level settings UI.
2021-08-19 21:04:24 +02:00
prefix=prefix}}
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
user_settings: Add a setting to display names of users who reacted. Added a setting to the bottom of Settings > Display settings > Theme section to display the reacting users on a message when numnber of reactions are small. This is a preparatory commit for #20980.
2022-04-08 16:04:22 +02:00
{{> settings_checkbox
setting_name="display_emoji_reaction_users"
is_checked=settings_object.display_emoji_reaction_users
label=settings_label.display_emoji_reaction_users
prefix=prefix}}
display_settings: Move the 'user-list-style' out of Emoji section. Move the 'user-list-style' checkbox from the 'Emoji' section to the 'Advanced' section, and update the 'settings_display.js' file by replacing the 'theme-settings' classname with 'advanced-settings' classname to display the success banner of 'user-list-style' checkbox with the 'Advanced' title.
2023-03-04 12:59:24 +01:00
</div>
<div class="advanced-settings {{#if for_realm_settings}}settings-subsection-parent{{else}}subsection-parent{{/if}}">
<div class="subsection-header">
<h3 class="light">{{t "Advanced" }}</h3>
{{> settings_save_discard_widget section_name="advanced-settings" show_only_indicator=(not for_realm_settings) }}
</div>
user_settings: Add user setting to control the user list style. Added a user_list_style personal user setting to the bottom of Settings > Display settings > Theme section which controls the look of the right sidebar user list. The radio button UI includes a preview of what the styles look like. The setting is intended to eventually have 3 possible values: COMPACT, WITH_STATUS and WITH_AVATAR; the final value is not yet implemented. Co-authored-by: Tim Abbott <tabbott@zulip.com>
2022-08-12 22:41:06 +02:00
user_settings: Add option to not mark messages as read on scroll. These changes introduces an new user option where it allows users read messages and scroll through their feed without marking those messages as read. Fixes: #22804.
2023-03-08 02:27:45 +01:00
<div class="input-group">
user_setting: Update wording for "Mark messages as read on scroll" setting. Previously, the user setting "Mark messages as read on scroll" sounded quite awkward and possibly confusing at times. We should update the text to something more clear and concise. This change will change "Mark messages as read on scroll" to "Automatically mark messages as read". The help center article is also fixed to name which setting is being adjusted.
2023-05-08 20:18:36 +02:00
<label for="web_mark_read_on_scroll_policy" class="dropdown-title">{{t "Automatically mark messages as read" }}
user_settings: Add option to not mark messages as read on scroll. These changes introduces an new user option where it allows users read messages and scroll through their feed without marking those messages as read. Fixes: #22804.
2023-03-08 02:27:45 +01:00
{{> ../help_link_widget link="/help/marking-messages-as-read" }}
</label>
<select name="web_mark_read_on_scroll_policy" class="setting_web_mark_read_on_scroll_policy prop-element settings_select bootstrap-focus-style" id="{{prefix}}web_mark_read_on_scroll_policy" data-setting-widget-type="number">
{{> dropdown_options_widget option_values=web_mark_read_on_scroll_policy_values}}
</select>
</div>
user_settings: Add user setting to control the user list style. Added a user_list_style personal user setting to the bottom of Settings > Display settings > Theme section which controls the look of the right sidebar user list. The radio button UI includes a preview of what the styles look like. The setting is intended to eventually have 3 possible values: COMPACT, WITH_STATUS and WITH_AVATAR; the final value is not yet implemented. Co-authored-by: Tim Abbott <tabbott@zulip.com>
2022-08-12 22:41:06 +02:00
<div class="input-group">
<label class="title">{{t "User list style" }}</label>
settings: Refactor code that handles radio type settings. This commit changes the settings code to consider the parent div of the radio inputs as prop-element and not individual input elements since all inputs are actually for a single setting. We still need to handle these settings as special cases at some places but that can also be fixed. As a result of this change, we can use ID to get setting name from the element in populate_data_for_request.
2022-09-30 16:24:36 +02:00
<div class="user_list_style_values grey-box prop-element" id="{{prefix}}user_list_style" data-setting-widget-type="radio-group" data-setting-choice-type="number">
user_settings: Add user setting to control the user list style. Added a user_list_style personal user setting to the bottom of Settings > Display settings > Theme section which controls the look of the right sidebar user list. The radio button UI includes a preview of what the styles look like. The setting is intended to eventually have 3 possible values: COMPACT, WITH_STATUS and WITH_AVATAR; the final value is not yet implemented. Co-authored-by: Tim Abbott <tabbott@zulip.com>
2022-08-12 22:41:06 +02:00
{{#each user_list_style_values}}
settings: Do not use bootstrap css in radio-type display settings. We rewrite the CSS rules, handled by bootstrap for the radio buttons in display settings (both user and realm-level defaults), to settings.css as we are in process of removing bootstrap. This commit adds a new class "display-settings-radio-choice-label" to radio label elements in the display settings and the bootstrap CSS rules along with existing CSS defined by us for radio-type display settings are added to this class. This change will help us in future where we may want to have reusable components (like settings_checkbox) for radio-type settings with visual preview. The line-height property added to input element by bootstrap is not added to settings.css since it is already added for all inputs in zulip.css.
2022-11-22 11:22:27 +01:00
<label class="display-settings-radio-choice-label">
settings: Refactor code that handles radio type settings. This commit changes the settings code to consider the parent div of the radio inputs as prop-element and not individual input elements since all inputs are actually for a single setting. We still need to handle these settings as special cases at some places but that can also be fixed. As a result of this change, we can use ID to get setting name from the element in populate_data_for_request.
2022-09-30 16:24:36 +02:00
<input type="radio" class="setting_user_list_style_choice" name="user_list_style" value="{{this.code}}"/>
user_settings: Add user setting to control the user list style. Added a user_list_style personal user setting to the bottom of Settings > Display settings > Theme section which controls the look of the right sidebar user list. The radio button UI includes a preview of what the styles look like. The setting is intended to eventually have 3 possible values: COMPACT, WITH_STATUS and WITH_AVATAR; the final value is not yet implemented. Co-authored-by: Tim Abbott <tabbott@zulip.com>
2022-08-12 22:41:06 +02:00
<span>{{this.description}}</span>
<span class="right preview">
{{#if (eq this.code 1)}}
<span class="user-name">{{../full_name}}</span>
css: Hyphenate .status-emoji selector.
2023-03-15 21:56:35 +01:00
<div class="emoji status-emoji emoji-1f3e0"></div>
user_settings: Add user setting to control the user list style. Added a user_list_style personal user setting to the bottom of Settings > Display settings > Theme section which controls the look of the right sidebar user list. The radio button UI includes a preview of what the styles look like. The setting is intended to eventually have 3 possible values: COMPACT, WITH_STATUS and WITH_AVATAR; the final value is not yet implemented. Co-authored-by: Tim Abbott <tabbott@zulip.com>
2022-08-12 22:41:06 +02:00
{{/if}}
{{#if (eq this.code 2)}}
<div class="user-name-and-status-text">
<div class="user-name-and-status-emoji">
<span class="user-name">{{../full_name}}</span>
{{> ../status_emoji emoji_code="1f3e0"}}
</div>
<span class="status-text">{{t "Working remotely" }}</span>
</div>
{{/if}}
</span>
</label>
{{/each}}
</div>
</div>
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
user_settings: Add option to disable escape key navigation to default view. Add `escape_navigates_to_default_view` as a bool setting in UserBaseSettings model and implement it as a checkbox that toggles the hotkey implementation of escape to the default view in the advanced user display settings. With /help/ documentation edits from Alya Abbott. Fixes #20043.
2021-10-25 19:17:19 +02:00
<div class="input-group thinner setting-next-is-related">
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
<label for="default_view" class="dropdown-title">{{t "Default view" }}
user_settings: Add option to disable escape key navigation to default view. Add `escape_navigates_to_default_view` as a bool setting in UserBaseSettings model and implement it as a checkbox that toggles the hotkey implementation of escape to the default view in the advanced user display settings. With /help/ documentation edits from Alya Abbott. Fixes #20043.
2021-10-25 19:17:19 +02:00
{{> ../help_link_widget link="/help/configure-default-view" }}
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="default_view" class="setting_default_view prop-element settings_select bootstrap-focus-style" id="{{prefix}}default_view" data-setting-widget-type="string">
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{> dropdown_options_widget option_values=default_view_values}}
</select>
</div>
user_settings: Add option to disable escape key navigation to default view. Add `escape_navigates_to_default_view` as a bool setting in UserBaseSettings model and implement it as a checkbox that toggles the hotkey implementation of escape to the default view in the advanced user display settings. With /help/ documentation edits from Alya Abbott. Fixes #20043.
2021-10-25 19:17:19 +02:00
{{> settings_checkbox
setting_name="escape_navigates_to_default_view"
is_checked=settings_object.escape_navigates_to_default_view
label=settings_label.escape_navigates_to_default_view
prefix=prefix}}
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
<div class="input-group">
<label for="demote_inactive_streams" class="dropdown-title">{{t "Demote inactive streams" }}
{{> ../help_link_widget link="/help/manage-inactive-streams" }}
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="demote_inactive_streams" class="setting_demote_inactive_streams prop-element settings_select bootstrap-focus-style" id="{{prefix}}demote_inactive_streams" data-setting-widget-type="number">
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{> dropdown_options_widget option_values=demote_inactive_streams_values}}
</select>
</div>
user_settings: Add new user setting to show/hide unread counts on streams. Added a show_unread_counts personal user setting to the Settings > Display settings > Advanced section which lets user choose whether he/she wants to see unread messages count on the left sidebar for streams. This setting have three options, "All Streams" - This will show unread messages count for all streams. "Unmuted Stream" - This will be default option and it will only show unread messages count for unmuted streams. "No Stream" - This option will not show unread messages count on any stream. Fixes #24149
2023-04-25 13:37:16 +02:00
<div class="input-group">
<label for="web_stream_unreads_count_display_policy" class="dropdown-title">{{t "Show unread counts for" }}</label>
<select name="web_stream_unreads_count_display_policy" class="setting_web_stream_unreads_count_display_policy prop-element bootstrap-focus-style settings_select" id="{{prefix}}web_stream_unreads_count_display_policy" data-setting-widget-type="number">
{{> dropdown_options_widget option_values=web_stream_unreads_count_display_policy_values}}
</select>
</div>
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{#each display_settings.settings.user_display_settings}}
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
{{> settings_checkbox
setting_name=this
is_checked=(lookup ../settings_object this)
label=(lookup ../settings_label this)
render_only=(lookup ../display_settings.render_only this)
prefix=../prefix}}
settings: Rearrange display settings. This provides a cleaner organization for our display settings, to make browsing them more intuitive for new users. We still need to update the /help/ documentation following this migration. Fixes #19960.
2021-10-21 14:11:19 +02:00
{{/each}}
settings: Create user_display_settings.hbs template. This commit creates a new template user_display_settings.hbs for user display settings and display_settings.hbs will be used as a common template for user-level and realm-level settings.
2021-08-19 16:38:10 +02:00
</div>
</form>