zulip/web/templates/settings/notification_settings_check...

<td>
    <label class="checkbox">
        <input type="checkbox" name="{{setting_name}}" id="{{prefix}}{{setting_name}}"
          {{#if (or is_muted is_disabled)}} disabled {{/if}}
          {{#if is_checked}}checked="checked"{{/if}} data-setting-widget-type="boolean"
          class="{{setting_name}}{{#unless is_disabled}} prop-element{{/unless}}"/>
        <span></span>
    </label>
</td>
settings: Migrate notification checkboxes to table format. Here we have migrated checkboxes of all general notifications to the table. By general notifications we mean, Mobile, Email, Desktop audio, and visual notifications. This is a part of a bigger migration to simply our notifications setting changing infrastructure for all streams and individual streams. Later we will add more row to this for different categories of notifications in addition to the current ones ("Streams" and "PMs, mentions, alerts"). Fixes: #12182. 2020-03-23 08:29:48 +01:00			`<td>`
			`<label class="checkbox">`
notification_settings: Display streams that differ. The user has an option for setting global notification settings as well as the same settings for individual streams. Currently the user has to keep track of each unmatched stream and then visit each individual stream whose settings he wants to update. Thus this adds a dedicated UI table allowing the user to view and update the notifications of the specific streams which differs from the global settings. It is located on the same page where the user defined global notification settings can be modified. Fixes #9228. 2020-03-12 17:40:38 +01:00			`<input type="checkbox" name="{{setting_name}}" id="{{prefix}}{{setting_name}}"`
settings: Grey out muted streams in personal settings. Muted streams are now greyed out in the personal settings, also changes to the notification settings of a muted stream are not possible anymore. Also, add a bell-slash icon after the stream name of muted streams, clicking on it unmutes the stream. Fixes #19780. 2021-11-20 11:51:35 +01:00			`{{#if (or is_muted is_disabled)}} disabled {{/if}}`
settings: Refactor frontend code for notification settings. This is a prep commit for adding UI for realm-level default of user settings. We refactor the code to use classes instead of ids such that we can use the common code for the new settings. 2021-08-09 13:26:49 +02:00			`{{#if is_checked}}checked="checked"{{/if}} data-setting-widget-type="boolean"`
settings: Use save-discard widget in realm-level defaults section. This commit adds save-discard widget in the realm-level defaults section. We use most of the functions used in settings_org.js by passing for_realm_default_settings and add conditionals according to it. Some of the major changes wrt to the organzation settings code are - - We use element name attribute here to get the setting name from element instead of id. We can add id for the elements here but there is a problem doing so for the emojiset setting as for the radio buttons we use four different input elements and all being for the same setting. - Added separate cases in discard_property_element_changes and get_input_element_value to handle the radio buttons. - We do not need get_complete_data_for_subsection here because all settings are controlled by single field in DB and single element in UI and thus we can simply get changed setting values from populate_data_for_request. - Added org-subsection-parent to the subsection container and prop-element to the input and select elements so that we can use the existing code. - Modified get_subsection_property_elements to just return the input element which is selected for emoji-settings subsection and not all the input elements because we only need the selected value of emojiset. We need other elements also when discarding the changes but we handle it separately. 2021-09-28 09:09:52 +02:00			`class="{{setting_name}}{{#unless is_disabled}} prop-element{{/unless}}"/>`
settings: Migrate notification checkboxes to table format. Here we have migrated checkboxes of all general notifications to the table. By general notifications we mean, Mobile, Email, Desktop audio, and visual notifications. This is a part of a bigger migration to simply our notifications setting changing infrastructure for all streams and individual streams. Later we will add more row to this for different categories of notifications in addition to the current ones ("Streams" and "PMs, mentions, alerts"). Fixes: #12182. 2020-03-23 08:29:48 +01:00			`<span></span>`
			`</label>`
			`</td>`