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
Zulip web now has a long list of buttons at the bottom of the compose box to help make it easy to insert markup for Zulip's many message-content features:
We should add more compose buttons too; not necessarily the exact same set as web, but a lot more than we currently have: just three, all for uploading files to attach to the message.
so this is mainly an umbrella issue for adding the various buttons.
The first prerequisite step will be to work out an idea of just what set of buttons we want. Then we can file separate issues for the individual buttons.
There's also one aspect of the design which we left out in #915, and will become necessary when we have a few more buttons:
the "..." overflow button, scrolling, and fading for excess compose buttons — for now we have just three of them, not enough to make those come into effect
This is an issue we won't get to before the app is launched, because the legacy app doesn't have those other buttons either.
The text was updated successfully, but these errors were encountered:
Zulip web now has a long list of buttons at the bottom of the compose box to help make it easy to insert markup for Zulip's many message-content features:
We should add more compose buttons too; not necessarily the exact same set as web, but a lot more than we currently have: just three, all for uploading files to attach to the message.
These buttons already appear in the design in Figma (cf #915):
https://www.figma.com/design/1JTNtYo9memgW7vV6d0ygq/Zulip-Mobile?node-id=3954-13395&m=dev
so this is mainly an umbrella issue for adding the various buttons.
The first prerequisite step will be to work out an idea of just what set of buttons we want. Then we can file separate issues for the individual buttons.
There's also one aspect of the design which we left out in #915, and will become necessary when we have a few more buttons:
This is an issue we won't get to before the app is launched, because the legacy app doesn't have those other buttons either.
The text was updated successfully, but these errors were encountered: