You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #5362 is for respecting the setting once a user has set it, perhaps through the web app. This issue is for offering UI to set it in the first place.
The existing UI for muting a topic, and for making a topic no longer muted, is in the topic action sheet, which you get by long-pressing on a topic. (Either on the inbox screen, or in the list of topics for a stream, or as the title in the app bar on a topic narrow's message list, or as a recipient header inside the message list.)
Probably that will be the natural place for the new UI too. Here's the UI we have planned for web (in zulip/zulip#24243 ):
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.
We should aim for something analogous in mobile. /cc @alya for thoughts on the desired UI.
The text was updated successfully, but these errors were encountered:
This is a companion to #5362, as part of the feature zulip/zulip#2517.
Issue #5362 is for respecting the setting once a user has set it, perhaps through the web app. This issue is for offering UI to set it in the first place.
The existing UI for muting a topic, and for making a topic no longer muted, is in the topic action sheet, which you get by long-pressing on a topic. (Either on the inbox screen, or in the list of topics for a stream, or as the title in the app bar on a topic narrow's message list, or as a recipient header inside the message list.)
Probably that will be the natural place for the new UI too. Here's the UI we have planned for web (in zulip/zulip#24243 ):
We should aim for something analogous in mobile. /cc @alya for thoughts on the desired UI.
The text was updated successfully, but these errors were encountered: