Duck Player: reportMetric support

[mgurgel]

Asana Task/Github Issue: https://app.asana.com/1/137249556945/task/1210602603977143?focus=true

Description

Implements the reportMetric shared method to increase observability of Duck Player

Testing Steps

• Simulate an error by using one of the mock test setups, or by passing willThrow=true to the Duck Player special page
• Check that a reportMetric message fires accordingly

Checklist

Please tick all that apply:

• I have tested this change locally
• I have tested this change locally in all supported browsers
• This change will be visible to users
• I have added automated tests that cover this change
• I have ensured the change is gated by config
• This change was covered by a ship review
• This change was covered by a tech design
• Any dependent config has been merged

[netlify]

✅ Deploy Preview for content-scope-scripts ready!

Name	Link
🔨 Latest commit	6c36057
🔍 Latest deploy log	https://app.netlify.com/projects/content-scope-scripts/deploys/687a50643956180008ff2a27
😎 Deploy Preview	https://deploy-preview-1766--content-scope-scripts.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

• Branch Name: pr-releases/pr-1766
• Commit Hash: 070612ef8b870647a0ce7f4283a86aec0d0c83c6
• Last Updated: July 18, 2025 at 1:47:57 PM UTC
• Install Command: npm i github:duckduckgo/content-scope-scripts#070612ef8b870647a0ce7f4283a86aec0d0c83c6

Please use the above install command to update to the latest version.

[github-actions]

[Beta] Generated file diff

Time updated: Fri, 18 Jul 2025 13:48:07 GMT

Android

    - android/contentScope.js

• android/pages/duckplayer/dist/index.js

File has changed

Integration

    - integration/contentScope.js

• integration/pages/duckplayer/dist/index.js

File has changed

Windows

    - windows/contentScope.js

• windows/pages/duckplayer/dist/index.js

File has changed

Apple

    - dist/contentScope.js

• dist/contentScopeIsolated.js
• dist/pages/duckplayer/dist/index.js
• dist/pages/duckplayer/index.html

File has changed

[shakyShane]

Just 1 thing to change with regards to how the init methods are called, other than that, looking really good 👍🏻

[mgurgel]

Regression tested on all platforms. The work supporting this on Android is due to go out next week.

[mgurgel]

@shakyShane @jonathanKingston Can we get this merged to Duck Player to unblock Android, and in the meantime I can flesh out the TD to potentially incorporate reportMetric into the messaging layer?

[cursor]

Bug: Error Handling Issues in Embed Creation

This commit introduces two bugs:

1. The ErrorBoundary's didCatch callback incorrectly accesses error?.error. The error parameter is the Error object itself, causing undefined to be passed to messaging.metrics.reportExceptionWithError and resulting in failed or incomplete exception reporting.
2. A null return from createEmbedSettings is now incorrectly treated as an error. This function's type annotation indicates null is a valid return, leading to Error('Embed not found') being thrown and reported as a false positive.

special-pages/pages/duckplayer/app/index.js#L78-L88

content-scope-scripts/special-pages/pages/duckplayer/app/index.js

Lines 78 to 88 in 6c36057

	embed = createEmbedSettings(window.location.href, settings);
	if (!embed) {
	throw new Error('Embed not found');
	}
	} catch (e) {
	messaging.metrics.reportException({ message: e.message, kind: EXCEPTION_KIND_INIT_ERROR });
	}
	const didCatch = (error) => {
	const message = error?.message;
	messaging.metrics.reportExceptionWithError(error?.error);

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎