Render text/html support attachments as links

[adalpari]

Description

Bot replies in the unified support screen can include text/html "citation" attachments — links to help articles (e.g. https://jetpack.com/support/...) rather than downloadable files.

Previously these were rendered as file cards with a generic page icon, and tapping one enqueued an Android DownloadManager download of the raw HTML — the wrong behavior for a web link. This is especially visible after a conversation is transferred to human support, where the bot's earlier messages render through the human-support path (file-card grid).

This PR introduces a new Link attachment type for text/html content and renders those attachments as tappable, underlined links (with an open-in-new icon) that open the URL in the browser:

• Model: text/html (case-insensitive) now maps to AttachmentType.Link. All other content types — including text/plain — keep their existing behavior.
• Human-support view (UnifiedAttachmentsList): link attachments are shown as a vertical list of links above the existing card grid; images/videos/other files are unchanged.
• Bot-conversation view (AttachmentRow): link filenames become tappable links; the citation match-score badge is preserved.
• Added a unit test covering the content-type → AttachmentType mapping.

Testing instructions

Before / after

/

NOTE: You might not be able to reproduce it since it entirely depends on the bot answers
Note2: use a non-free account

1. Enable the new support FF
2. Open a bot conversation and act generic like "test" "new test" so you hopefully get some links

• Verify you can click the links

3. Ask to talk to a human
4. Your conversation should be escalated and the UI changes

• Verify you properly see the links and can click them.

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Android by scanning the QR code below to install the corresponding build.

	App Name	WordPress Android
	Build Type	Debug
	Version	pr23011-24da00c
	Build Number	1497
	Application ID	org.wordpress.android.prealpha
	Commit	24da00c
	Installation URL	1j8sjb9opbgig

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Android by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Android
	Build Type	Debug
	Version	pr23011-24da00c
	Build Number	1497
	Application ID	com.jetpack.android.prealpha
	Commit	24da00c
	Installation URL	31bugq35dod70

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[codecov]

Codecov Report

❌ Patch coverage is 9.58904% with 66 lines in your changes missing coverage. Please review.
✅ Project coverage is 37.41%. Comparing base (400d4d2) to head (24da00c).

Files with missing lines	Patch %	Lines
...port/unified/ui/UnifiedConversationDetailScreen.kt	0.00%	66 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            trunk   #23011      +/-   ##
==========================================
- Coverage   37.42%   37.41%   -0.01%     
==========================================
  Files        2325     2325              
  Lines      125399   125451      +52     
  Branches    17205    17213       +8     
==========================================
+ Hits        46929    46942      +13     
- Misses      74656    74694      +38     
- Partials     3814     3815       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nbradbury]

@adalpari I've not tested this yet, but Claude had some suggestions:

Accessibility gap in the bot-view link (AttachmentRow). UnifiedAttachmentLink gets a descriptive contentDescription (“Open link: …”), but the clickable Text in AttachmentRow does not — a screen reader just reads the filename with no indication it’s an actionable link. Consider adding the same semantics/contentDescription (and ideally Role.Button/link) there for parity.

openUri can throw ActivityNotFoundException. This is the only LocalUriHandler.openUri usage in the app, so there’s no established pattern. If no browser/handler exists (or the URL is malformed), uriHandler.openUri(...) throws and crashes the screen. Low likelihood on real devices, but worth a runCatching {} with a graceful no-op/toast given this is bot-supplied data you don’t fully control.

[nbradbury]

When I click a link, it correctly takes me to the web page, but when I click back it just shows an empty screen. I click back again and I see the "Get Help" screen but it never loads.

screen.mov

[adalpari]

@nbradbury I've made some changes. Can you give it another go?

[nbradbury]

@adalpari I'm still seeing the issue with the back button and it turns out it was due to having "Don't keep activities" enabled, so it's something users are unlikely to experience. I had Claude write up a plan for resolving it in case you want to address the problem, but I'll go ahead an approve.

[nbradbury]

[adalpari]

@adalpari I'm still seeing the issue with the back button and it turns out it was due to having "Don't keep activities" enabled, so it's something users are unlikely to experience. I had Claude write up a plan for resolving it in case you want to address the problem, but I'll go ahead an approve.

Cool!
Well, I don't think that's a case we want to "solve". I mean, if someone has enabled "don't keep" activities, then that behaviour is expected.

[wpmobilebot]

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.