[$250] Chat- Thread message is not shown in the detail page

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.63-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #73242
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy S10/ Chrome
App Component: Chat Report View

Action Performed:

1. Navigate to staging.new.expensify.com
2. Open a chat
3. Send a message - <div>test<div>
4. Long press and open reply thread
5. Go to thread header and open header page

Expected Result:

The Header title and the detail page have same name as the sent message

Actual Result:

The detail page doesn't have the same name as the title

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug7012446_1764017184207.Screen_Recording_20251124_234609_Chrome.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021993243465376637566
• Upwork Job ID: 1993243465376637566
• Last Price Increase: 2025-11-25

Issue Owner

Current Issue Owner: @yuwenmemon

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021993243465376637566

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

[jliexpensify]

I can repro, but may get an Engineering opinion on whether this is a real bug?

[thelullabyy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The detail page doesn't have the same name as the title

What is the root cause of that problem?

We're using

const reportName = Parser.htmlToText(getReportName(report, undefined, undefined, undefined, undefined, reportAttributes));

in ReportDetailsPage to show the reportName, so it'll convert the <div>test</div> to test

What changes do you think we should make in order to solve the problem?

we should use safeEscape before calling htmlToText

    const reportName = Parser.htmlToText(Str.safeEscape(getReportName(report, undefined, undefined, undefined, undefined, reportAttributes)));

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[lorretheboy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The detail page doesn't have the same name as the title

What is the root cause of that problem?

In HeaderView, there's logic to preserve HTML formatting for thread names from ADD_COMMENT actions by setting shouldParseFullTitle = false

But in ReportDetailsPage.tsx, the report name was always being parsed to text using Parser.htmlToText(), regardless of the action type

App/src/pages/ReportDetailsPage.tsx

Line 338 in 2ed5230

const reportName = Parser.htmlToText(getReportName(report, undefined, undefined, undefined, undefined, reportAttributes));

What changes do you think we should make in order to solve the problem?

We should match the behavior in HeaderView. This is used to ensure that we display the text exactly as the user entered it when displaying thread header text, instead of parsing their text to HTML.

    const shouldParseReportName = parentReportAction?.actionName !== CONST.REPORT.ACTIONS.TYPE.ADD_COMMENT;
    const reportNameRaw = getReportName(report, undefined, undefined, undefined, undefined, reportAttributes);
    const reportName = shouldParseReportName ? Parser.htmlToText(reportNameRaw) : reportNameRaw;

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[eVoloshchak]

I suggest we put this on HOLD for #68721, this might be resolved there