Fix issue where context is not attach on first use

[aitorvs]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1211654189969294/task/1213386554167128?focus=true

Description

On first time use the page content is not attached.

Repro steps:

• fresh install and go through onboarding to get to the point where contextual can be used
• go to eg. bbc.com and tap on duck.ai icon to open the contextual sheet
• sheet opens and shows the first time run
• "attach page content" placeholder is shown alongside the chip suggestions
• tap on the "summarize" suggestion chip OR tap on placeholder
• Expected: content is attached
• ❌ Actual: content is NOT attached

Steps to test this PR

The following repro steps should now work

Repro steps:

• fresh install and go through onboarding to get to the point where contextual can be used
• go to eg. bbc.com and tap on duck.ai icon to open the contextual sheet
• sheet opens and shows the first time run
• "attach page content" placeholder is shown alongside the chip suggestions
• tap on the "summarize" suggestion chip OR tap on placeholder
• Expected: content is attached
• ❌ Actual: content is NOT attached

---

Note

Low Risk
Small, localized change to when a JS subscription event is emitted; main risk is timing/regression in contextual sheet analytics or page-context attachment triggering.

Overview
Fixes first-run Duck.ai contextual mode not attaching page content by triggering page-context collection when the contextual bottom sheet is shown.

Moves the page-context subscription event send out of the omnibar click path into a new BrowserTabViewModel.collectPageContext() called from BrowserTabFragment.showDuckChatContextualSheet, and adds unit tests to verify the event is emitted only when explicitly collecting context (and not during onboarding).

^{Written by Cursor Bugbot for commit 7f779d0. This will update automatically on new commits. Configure here.}

[aitorvs]

• Fix issue where context is not attach on first use #7790 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[malmstein]

@aitorvs I’ve made a few changes, mostly consolidating when the page context is collected to make sure it’s always there. Take a look and we can discuss.

[daxmobile]

📝 [actionlint] _{reported by reviewdog 🐶}
shellcheck reported issue in this script: SC2086:info:6:27: Double quote to prevent globbing and word splitting [shellcheck]

Android/.github/workflows/release_create_tag.yml

Line 58 in 137b396

run: |

[daxmobile]

📝 [actionlint] _{reported by reviewdog 🐶}
shellcheck reported issue in this script: SC2086:info:3:32: Double quote to prevent globbing and word splitting [shellcheck]

Android/.github/workflows/release_create_tag.yml

Line 68 in 137b396

run: |

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

PLACEHOLDER validation removed but default value remains

Low Severity

The PLACEHOLDER input validation check was removed from release_create_task.yml, but the workflow_dispatch input still has default: 'PLACEHOLDER' on line 15. While the orchestrator workflow runs release_create_tag.yml first (which now has the check), release_create_task.yml can still be triggered independently via manual dispatch. A manual trigger without changing the default would create an Asana task named "Android Release PLACEHOLDER".

---

_{Please tell me if this was useful or not with a 👍 or 👎.}

 

[joshliebe]

Works well, LGTM 👍