Skip to content

Docs updates for E/A#90516 Update edit message docs for composer on narrow screens#90808

Closed
MelvinBot wants to merge 1 commit into
mainfrom
melvin-docs-updates-90516
Closed

Docs updates for E/A#90516 Update edit message docs for composer on narrow screens#90808
MelvinBot wants to merge 1 commit into
mainfrom
melvin-docs-updates-90516

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Summary

  • Updates the "Edit or Delete Messages" section in Chat-Features-and-Moderation-Tools.md to reflect the new editing behavior introduced in Allow editing messages in Composer on narrow screens V2 #90516
  • On mobile/narrow screens, selecting Edit comment now populates the bottom composer instead of inline editing
  • Separates desktop and mobile instructions per HelpDot naming conventions (platform-specific flows require separate instructions)

Related PR

#90516

Reflect the new editing UX where mobile/narrow screens use the bottom
composer instead of inline editing when editing a message.

Co-authored-by: Christoph Pader <chrispader@users.noreply.github.com>
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label May 15, 2026
@stephanieelliott stephanieelliott marked this pull request as ready for review May 20, 2026 00:11
@stephanieelliott stephanieelliott self-requested a review as a code owner May 20, 2026 00:11

**To edit or delete a message:**

**On Desktop:**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naming convention mismatch: The navigation instruction standards in HELPSITE_NAMING_CONVENTIONS.md use "Web:" and "Mobile:" as the canonical platform labels (see "If Web and Mobile Navigation Differ" section). This should read **Web:** instead of **On Desktop:** to stay consistent with the governance standard.

3. Select **Edit comment** or **Delete comment**.
4. If editing, modify the message inline and click **Save**.

**On Mobile:**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naming convention mismatch: Same as above -- the governance standard in HELPSITE_NAMING_CONVENTIONS.md uses the label format Mobile: (not On Mobile:). Consider changing to **Mobile:** for consistency with the established pattern.

@github-actions
Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR updates the "Edit or Delete Messages" section to document platform-specific editing behavior following the composer change on narrow/mobile screens (E/A#90516). The change is small, well-scoped, and correctly separates Desktop and Mobile instructions per governance conventions.

Scores Summary

  • Readability: 9/10 - Steps are clear, sequential, and action-oriented. The mobile step 4 is slightly long but remains understandable. Good parallel structure between Desktop and Mobile blocks.
  • AI Readiness: 8/10 - The changes sit under the existing # Edit or Delete Messages heading, which is not task-based (governance requires action verbs or question words for headings). However, this heading is pre-existing and not part of the proposed diff, so no deduction is applied to the changes themselves. The new content uses full feature-specific language that supports retrieval.
  • Style Compliance: 9/10 - Button names (Edit comment, Delete comment, Save, Send) are correctly bolded and match UI terminology. Platform labels follow the pattern already established in the article. One minor note: the governance document uses "Web" and "Mobile" as platform labels, while this article (both old and new content) uses "Desktop" and "Mobile". This is consistent within the article but slightly diverges from the governance wording.

Key Findings

  • The platform-specific separation is the correct approach per HELPSITE_NAMING_CONVENTIONS.md ("If Web and Mobile Navigation Differ -- Provide separate instructions").
  • All UI element references are properly bolded and appear to use exact UI labels.
  • The mobile step 4 provides helpful context about the composer behavior, which is the core purpose of this documentation update.
  • The "Desktop" vs "Web" label usage is consistent with the rest of the article but differs from governance guidance which uses "Web" terminology. This is a pre-existing pattern in the file and may warrant a separate cleanup pass.

Recommendations

  • Consider whether "On Desktop" should be "On Web" to align with governance language (HELPSITE_NAMING_CONVENTIONS.md references "Web" and "Mobile"). This applies to both the new and existing platform labels in the file, and could be addressed in a follow-up PR.
  • Optional: The mobile step 4 could be slightly tightened. For example: "If editing, edit the message in the composer at the bottom of the screen, then tap the Send icon." This removes the explanatory clause about the text appearing, keeping it more action-focused per the step formatting standard.

Files Reviewed

  • docs/articles/new-expensify/chat/Chat-Features-and-Moderation-Tools.md -- Platform-specific edit/delete instructions added; compliant with governance standards.

Review based on docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md.

1. Open a chat.
2. Long-press a message.
3. Select **Edit comment** or **Delete comment**.
4. If editing, the message text appears in the composer at the bottom of the screen. Edit it there, then tap the **Send** icon to save your changes.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability / step formatting: This step is doing a lot of work -- it describes where the text appears, instructs the user to edit, and then instructs them to tap Send. Per the step formatting standard (HELP_AUTHORING_GUIDELINES.md Section 5), steps should be clear and action-oriented. Consider splitting into two steps for clarity:

4. Edit the message in the composer at the bottom of the screen.
5. Tap the **Send** icon to save your changes.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2271c62e9c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

1. Open a chat.
2. Long-press a message.
3. Select **Edit comment** or **Delete comment**.
4. If editing, the message text appears in the composer at the bottom of the screen. Edit it there, then tap the **Send** icon to save your changes.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use the correct submit icon name for mobile edits

On narrow/mobile layouts, editing a message changes the composer button from Send to Save changes with a checkmark icon (src/pages/inbox/report/ReportActionCompose/ComposerSendButton.tsx sets icon = icons.Checkmark and label = common.saveChanges when editing). This step currently tells users to tap the Send icon, which can misdirect them during the exact flow this update is documenting.

Useful? React with 👍 / 👎.

@stephanieelliott
Copy link
Copy Markdown
Contributor

I don't think this is needed, feature is pretty intuitive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants