Reader: Collapse long comments

[kean]

Reader will now collapse long comments. You can tap "Show More" to expand.

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 26.6. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

[wpmobilebot]

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

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	30546
	Version	PR #25156
	Bundle ID	org.wordpress.alpha
	Commit	2ea2c53
	Installation URL	64cs06gkdkve8

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 by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	30546
	Version	PR #25156
	Bundle ID	com.jetpack.alpha
	Commit	2ea2c53
	Installation URL	63j7272pon03o

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

[crazytonyli]

I think this constraint may cause conflicts if the font is super large? Instead of hard-code a height here, would setting the button.contentInsets or the margins between the button and its parent view work?

[crazytonyli]

Nitpick: use a lazy var to avoid optional

[crazytonyli]

Nitpick:

Suggested change

	gradientLayer.frame = bounds
	gradientLayer.frame = layer.bounds

[kean]

Oh, sorry I didn't mean to send it for a review yet. Let me fix a couple of things, and re-send it.

[wpmobilebot]

🤖 Build Failure Analysis

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

[kean]

I reworked and retested the implementation.

I think this constraint may cause conflicts if the font is super large? Instead of hard-code a height here, would setting the button.contentInsets or the margins between the button and its parent view work?

I set maximum supported category size for the button, so it looks acceptable under all conditions.

Nitpick: use a lazy var to avoid optional

Made overlay optional.

Additional changes:

• Fix race condition in WebCommentContentRenderer where it would sometimes call delegate with a old height for the previous comment
• Tweak the "collapse" behavior so if it only collapses comments if there is enough stuff to put under the fold (120 pt+)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud