-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages with whitespace-only topics should not be sent #3743
Comments
Fixes zulip#3743. This trims the topic string whenever the message text input is focused. Apart from preventing whitespace-only topics from sending, it will also remove whitespace from the start and end of the topic string like Zulip web version.
Fixes zulip#3743. This trims the topic string whenever the message text input is focused. Apart from preventing whitespace-only topics from sending, it will also remove whitespace from the start and end of the topic string like Zulip web version.
Fixes zulip#3743. This trims the topic string whenever the message text input is focused. Apart from preventing message with whitespace-only topic from sending, it will also remove whitespace from the start and end of the topic string like Zulip web version.
Fixes zulip#3743. This disables the floating button until the valid topic string is inserted.
This reverts commit a2d6793. Fixes zulip#3820 (Send button never enabled in PMs), which was a regression induced by the reverted commit. Reopens zulip#3743.
Reopened by the revert in #3837. |
The original fix #3748 caused #3820. See #3821 (comment) for a bit more discussion on how the logic might work here. |
Hmm. When the topic input is completely empty, we allow sending the message -- the server just turns the topic into "(no topic)". That mirrors the webapp. Seems like when the topic input consists of whitespace, we should just treat that as an empty topic: you can send just fine, but we'll strip the whitespace, and the server will turn the topic into "(no topic)". More generally, we should strip leading and trailing whitespace in the topic. Reassuringly, that also seems to be what the webapp does, so we'd be matching its behavior. |
Trim the leading and trailing whitespace from topic while sending a message in the ComposeBox. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes zulip#3743.
Trim the leading and trailing whitespace from topic on sending a message in the ComposeBox. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes zulip#3743.
Trim the leading and trailing whitespace from topic when used by `getDestinationNarrow()`. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes zulip#3743.
Bumping priority because this is one of the handful of most frequent errors in our Sentry logs. |
Trim the leading and trailing whitespace from topic when used by `getDestinationNarrow()`. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes #3743.
Trim the leading and trailing whitespace from topic when used by `getDestinationNarrow()`. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes zulip#3743. docs/release: Submit early for App Store review. This saves some latency. If we had a lot of beta releases we never send to prod, there might be value in skipping App Store review for those, but we don't. UI description is a bit approximate because I don't have it in front of me. When I do the next release, I'll be able to see the UI again and can fill in the exact text of things.
Trim the leading and trailing whitespace from topic when used by `getDestinationNarrow()`. A consequence of this is that a whitespace-only topic gets converted to '(no topic)'. Fixes zulip#3743.
It should not be possible to attempt to send a message with a topic consisting only of whitespace.
Note: this bug interacts with #3731. If an attempt is made to post such a message, then – while such messages remain in the outbox – any future messages with empty topic will be unified with that topic, instead of being given the topic
(no topic)
as they ordinarily would.The text was updated successfully, but these errors were encountered: