Skip to content

Conversation

chrisbobbe
Copy link
Collaborator

@chrisbobbe chrisbobbe requested a review from gnprice August 5, 2025 20:56
@chrisbobbe chrisbobbe added the integration review Added by maintainers when PR may be ready for integration label Aug 5, 2025
@gnprice
Copy link
Member

gnprice commented Aug 6, 2025

Thanks! Looks good; merging.

@gnprice gnprice force-pushed the pr-mark-channel-as-read-first branch from a2fd25f to 766f071 Compare August 6, 2025 23:18
@gnprice gnprice merged commit 766f071 into zulip:main Aug 6, 2025
1 check failed
@chrisbobbe chrisbobbe deleted the pr-mark-channel-as-read-first branch August 6, 2025 23:19
chrisbobbe added a commit to chrisbobbe/zulip-flutter that referenced this pull request Sep 25, 2025
…send

This fixes part of the "second buggy behavior" that I described
in zulip#1789: specifically, it fixes that behavior when the self-user
doesn't have permission to send messages in the channel.

Later, for the case where there *is* permission to send messages, we
should use a different banner label, like "Replies to your messages
will not appear automatically." I think it's smoothest not to touch
that case until we've fixed the "first" and "third" parts of zulip#1798,
because those are bugs in the send-message experience.

Fixes-partly: zulip#1798
chrisbobbe added a commit to chrisbobbe/zulip-flutter that referenced this pull request Oct 1, 2025
…send

This fixes part of the "second buggy behavior" that I described
in zulip#1789: specifically, it fixes that behavior when the self-user
doesn't have permission to send messages in the channel.

Later, for the case where there *is* permission to send messages, we
should use a different banner label, like "Replies to your messages
will not appear automatically." I think it's smoothest not to touch
that case until we've fixed the "first" and "third" parts of zulip#1798,
because those are bugs in the send-message experience.

Fixes-partly: zulip#1798
chrisbobbe added a commit to chrisbobbe/zulip-flutter that referenced this pull request Oct 9, 2025
…send

This fixes part of the "second buggy behavior" that I described
in zulip#1789: specifically, it fixes that behavior when the self-user
doesn't have permission to send messages in the channel.

Later, for the case where there *is* permission to send messages, we
should use a different banner label, like "Replies to your messages
will not appear automatically." I think it's smoothest not to touch
that case until we've fixed the "first" and "third" parts of zulip#1798,
because those are bugs in the send-message experience.

Fixes-partly: zulip#1798
chrisbobbe added a commit to chrisbobbe/zulip-flutter that referenced this pull request Oct 9, 2025
…send

This fixes part of the "second buggy behavior" that I described
in zulip#1789: specifically, it fixes that behavior when the self-user
doesn't have permission to send messages in the channel.

Later, for the case where there *is* permission to send messages, we
should use a different banner label, like "Replies to your messages
will not appear automatically." I think it's smoothest not to touch
that case until we've fixed the "first" and "third" parts of zulip#1798,
because those are bugs in the send-message experience.

Fixes-partly: zulip#1798
gnprice pushed a commit to chrisbobbe/zulip-flutter that referenced this pull request Oct 10, 2025
…send

This fixes part of the "second buggy behavior" that I described
in zulip#1789: specifically, it fixes that behavior when the self-user
doesn't have permission to send messages in the channel.

Later, for the case where there *is* permission to send messages, we
should use a different banner label, like "Replies to your messages
will not appear automatically." I think it's smoothest not to touch
that case until we've fixed the "first" and "third" parts of zulip#1798,
because those are bugs in the send-message experience.

Fixes-partly: zulip#1798
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration review Added by maintainers when PR may be ready for integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants