Zixuan Li
Zixuan Li
It is totally possible for Pygments to [generate HTML elements with more than one classes](https://github.com/pygments/pygments/blob/07b69d42ca431249250195e7f7fbd21e1ccdfb2c/pygments/formatters/html.py#L853-L855). This is considered quite an edge case and only happens to some languages, such as...
When a timestamp is created in a broken format (such as ``), the server generates a `span` element with the `timestamp-error` class. We should handle that and display something like...
When you type send a message like `/me content`, the message gets rendered differently where the text appears directly after the user name. Related zulip-mobile issue: #https://github.com/zulip/zulip-mobile/issues/1773 Low priority because...
This supports the new UX of disabling the topic input, content input and the buttons on the compose box when sending a message, and only re-enable them and clearing the...
We then should be able to remove `streamName` from `FcmMessageChannelRecipient`. See also: - https://github.com/zulip/zulip/pull/18067 - https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/Possible.20deprecation.20of.20stream.20name.20in.20push.20notifications
[PostgresLexer](https://github.com/pygments/pygments/blob/07b69d42ca431249250195e7f7fbd21e1ccdfb2c/pygments/lexers/sql.py#L182) (added in https://github.com/pygments/pygments/commit/4e878a0d8bd39450028938295d52436c630fef4d) can generate `String.Name`, which is not included in `pygments.token.STANDARD_TYPES`. Not sure if this is intended, but for this input ``` " ``` it produces something like...
To reproduce: 1. Go to the starred messages view on the mobile app 2. Log into the same account on another device 3. Star an old message I haven't yet...
Stacked on top of #1491. Some non-goals of this change are deferred to #1499. In this implementation, we fetch the topics but do not handle all events to receive live-updates....
screenshots | message sent | got message event | | - | - | |  |  | | message failed to send | message content tapped | recipient...
This is stacked atop #1463, toward #1441. No UI/user-facing change in this PR.