diff --git a/api_docs/changelog.md b/api_docs/changelog.md index 6ef51857c4..4e6839cafb 100644 --- a/api_docs/changelog.md +++ b/api_docs/changelog.md @@ -101,8 +101,9 @@ format used by the Zulip server that they are interacting with. * [`POST /register`](/api/register-queue), [`PATCH /settings`](/api/update-settings), [`PATCH /realm/user_settings_defaults`](/api/update-realm-user-settings-defaults): - Added new user setting `web_mark_read_on_scroll_policy` . This determines whether to mark - messages as read or not as the client scrolls through their feed. + Added new user setting `web_mark_read_on_scroll_policy`. Clients may use this to + determine the user's preference on whether to mark messages as read or not when + scrolling through their message feed. **Feature level 174**: diff --git a/zerver/openapi/zulip.yaml b/zerver/openapi/zulip.yaml index 361e3dca28..94aff8cf29 100644 --- a/zerver/openapi/zulip.yaml +++ b/zerver/openapi/zulip.yaml @@ -9392,15 +9392,16 @@ paths: - name: web_mark_read_on_scroll_policy in: query description: | - Whether or not to mark messages as read when the client scrolls through their + Whether or not to mark messages as read when the user scrolls through their feed. - 1 - Always - 2 - Only in conversation views - 3 - Never - **Changes**: New in Zulip 7.0 (feature level 175). Previously, the app behaved - like the "Always" setting, without any way to configure this. + **Changes**: New in Zulip 7.0 (feature level 175). Previously, there was no + way for the user to configure this behavior on the web, and the Zulip web and + desktop apps behaved like the "Always" setting when marking messages as read. schema: type: integer enum: @@ -11504,15 +11505,16 @@ paths: web_mark_read_on_scroll_policy: type: integer description: | - Whether or not to mark messages as read when the client scrolls through their + Whether or not to mark messages as read when the user scrolls through their feed. - 1 - Always - 2 - Only in conversation views - 3 - Never - **Changes**: New in Zulip 7.0 (feature level 175). Previously, the app behaved - like the "Always" setting, without any way to configure this. + **Changes**: New in Zulip 7.0 (feature level 175). Previously, there was no + way for the user to configure this behavior on the web, and the Zulip web and + desktop apps behaved like the "Always" setting when marking messages as read. starred_message_counts: type: boolean description: | @@ -13471,15 +13473,16 @@ paths: web_mark_read_on_scroll_policy: type: integer description: | - Whether or not to mark messages as read when the client scrolls through their + Whether or not to mark messages as read when the user scrolls through their feed. - 1 - Always - 2 - Only in conversation views - 3 - Never - **Changes**: New in Zulip 7.0 (feature level 175). Previously, the app behaved - like the "Always" setting, without any way to configure this. + **Changes**: New in Zulip 7.0 (feature level 175). Previously, there was no + way for the user to configure this behavior on the web, and the Zulip web and + desktop apps behaved like the "Always" setting when marking messages as read. starred_message_counts: type: boolean description: | @@ -14428,15 +14431,16 @@ paths: - name: web_mark_read_on_scroll_policy in: query description: | - Whether or not to mark messages as read when the client scrolls through their + Whether or not to mark messages as read when the user scrolls through their feed. - 1 - Always - 2 - Only in conversation views - 3 - Never - **Changes**: New in Zulip 7.0 (feature level 175). Previously, the app behaved - like the "Always" setting, without any way to configure this. + **Changes**: New in Zulip 7.0 (feature level 175). Previously, there was no + way for the user to configure this behavior on the web, and the Zulip web and + desktop apps behaved like the "Always" setting when marking messages as read. schema: type: integer enum: