We chose not to edit the original markdown files to make this change
since the conversion script logic can be used for removing these lines
with very little changes and we don't need the original markdown source
files to be edited before the cutover.
The css for making loose and ordered lists look same has been removed
since we wanted to to respect commonmark specification.
UTF-8 is far and wide the dominant encoding, so we assume that
encoding if we have more than 66% confidence -- this allows it to be
guessed even for short files. ISO-8859-1 caps at 73% confidence, so
we assume that if it's the best option and it hits that max.
Otherwise, we still require 90% confidence.
This commit updates the data that gets encrypted to be
the same on both android and iOS.
The data and its format is almost the same as what we send
as FCM payload to android clients with no E2EE support,
changes are:
For send push notification payload:
* 'realm_id`, 'server', 'sender_email', and 'realm_uri' fields
don't exist in the new payload.
* 'event' field renamed to 'type'
* 'stream' and 'stream_id' fields renamed to 'channel_name'
and 'channel_id' respectively.
* The value of 'recipient_type' will be 'channel' & 'direct'
instead of 'stream' & 'private' respectively.
* 'zulip_message_id' field renamed to 'message_id'
For remove push notification payload:
* 'realm_id`, 'server', and 'realm_uri' fields don't exist
in the new payload.
* 'event' field renamed to 'type'
* 'zulip_message_ids' field renamed to 'message_ids' and it's
value will be a JSON array instead of a string.
In the existing iOS client, we have no code of our own involved
in constructing the notifications in the UI, and instead we
leave it to the iOS SDK to do so.
Since, for clients with E2EE support the data is going to be
interpreted by our own code, not by the iOS SDK - we are free
to keep the same data and format.
Co-authored-by: Tim Abbott <tabbott@zulip.com>
This commit removes the 'zulip_message_id' field from the FCM
payload for remove push notification.
Clients that use `zulip_message_ids` instead have been out for
years and we no longer support older client versions that don't.
Add a check for window blur and save any in-progress
messages as drafts. This will help prevent unnecessary
message loss for the user by creating drafts for them more
whenever they switch away from their Zulip tab.
Tested on my local Ubuntu development with a demo
organization and some of the premade profiles.
Fixes#35262.
It is possible for us to scroll user back to top of view if they
scroll before the render is complete and we haven't called
`revive_current_focus` yet.
This fixes it by wrapping the render and revive logic in a single
animation frame so that any scroll requests are delayed until we
have completed both of them.
This commit adds 'highlighted-element' class to <b> tags in
the following parts of the settings panel:
* who can access channel
* user member of a user group because of being part of a subgroup
already added.
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
This commit adds 'highlighted-element' class to <b> tags in
the following compose banners:
* jump_to_sent_message_conversation_banner
* stream_does_not_exist_error
* unknown_zoom_user_error
* channel wildcard_mention_not_allowed_error
* topic wildcard_mention_not_allowed_error
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
This commit adds 'highlighted-element' class to <b> tags in
the following left sidebar popovers:
* inbox
* combined feed
* recent conversations
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
This commit adds 'highlighted-element' class to <b> tags in
the following confirm dialogs:
* delete topic
* mute user
* join user group
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
We are porting the current help center docs to the new help center.
Porting the display_host variable to the new help center is a tricky
task and it is not worth to put in the effort for that just for 3 uses
of that variable.
This commit ensures that the focus on the topic list search box is only
triggered when the user clicks on the "SHOW ALL TOPICS" button, and not
when the narrow changes. This prevents unwanted focus behavior when
switching between different narrows/views which interfered with the
focus states of the compose box.
Fixes#20028.
There's no reason to have a special `RealmCreationKey` class - the
`Confirmation` system already does this job.
This is somewhat complicated by the need to write a migration for
`RealmCreationKey`->`Confirmation` for pre-existing, valid objects, to
avoid breaking realm creation links that haven't been used yet.
Clears up some naming confusion - `REALM_CREATION_LINK_VALIDITY_DAYS` is
a setting which describes the validaty period of RealmCreationKey, not
of Confirmation with REALM_CREATION type. Now that the latter is called
NEW_REALM_USER_REGISTRATION, there should be no confusion about this.
This commit refactors to import the full
`left_sidebar_navigation_area` module instead of
individual functions. This allows calling multiple
functions easily and prepares for upcoming navigation
view changes.
This commit adds 'highlighted-element' class to <b> tags in
the following onboarding modals:
* introduce inbox view modal
* introduce recent conversations view modal
* introduce resolve topic modal
* introduce first channel created modal
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
