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
Via zulip/zulip#8061, we recently added Zulip webapp support for picking a notification sound from a set of (currently) 2 choices. Before doing mobile work on this, we should wait for the server/client API to work how we want it to (right now, we send just a name, e.g. "ding", to tell a client what sound to use, and I think we should instead send a dictionary structure mapping available sound file formats to full sound URLs, as described in zulip/zulip#8061 (comment)), but I'm opening the mobile issue now so that we don't forget about it.
The text was updated successfully, but these errors were encountered:
I suspect this will be more complicated on mobile than it sounds to be useful if implemented fully flexibly like that.
What if we just supply the files up front and the only option given is one of the names?
Via zulip/zulip#8061, we recently added Zulip webapp support for picking a notification sound from a set of (currently) 2 choices. Before doing mobile work on this, we should wait for the server/client API to work how we want it to (right now, we send just a name, e.g. "ding", to tell a client what sound to use, and I think we should instead send a dictionary structure mapping available sound file formats to full sound URLs, as described in zulip/zulip#8061 (comment)), but I'm opening the mobile issue now so that we don't forget about it.
The text was updated successfully, but these errors were encountered: