2027637 - Some of the Intent, Mentions and Input Telemetry events show incorrect values

Status: RESOLVED FIXED

(Core :: Machine Learning: Frontend, defect)

Description

[Rares Doghi, Desktop QA]

Found in

• Nightly 151.0a1 (2026-03-29)

Affected versions

• Nightly 151.0a1 (2026-03-29)
• Beta 150.0b2

Affected platforms

• all

Steps to reproduce

1. Open a Smart Window.
2. Trigger the following TElemetry events:

navigate_submit
chat_submit
search_submit
smart_bar_intent_change_preview
add_tabs_click
add_tabs_selection
remove_tab
mention_start
mention_select
mention_remove

Expected result

• The Telemetry events are fired and they contain the correct values

Actual result

• The following issues have been encountered:

navigate_submit: (No Data to display)
does not fire if we Type www.gamespot.com and then Hit Enter Directly
does not fire for search or anything.
submit_type does not work correctly, it will not identify the Button click instead of Enter.

chat_submit:
no tokens value displayed
memories values not displayed
Submit Type will not register that I clicked the Ask button instead of Enter.
asking from the Address bar will show Tabs - 0
Location is not registered from the address bar.

search_submit:
detected intent was incorrect, intent was ask while the user selected the search
search from the address bar is not detected

add_tabs_click:
Tabs preselected will not record 1 only if 2 or more are preselected in which case for 2 tabs added it will show 1 preselected tab (not sure if its ok, technically its true if we already add 1 tab 1 is already there preselected.)
"message_seq": does this count users prompt as well ? for 1 user prompt and 1 response from the ai its counted as 2 message_seq

Regression range
N/A

Comment 2

[Florian Zia [:flozia]]

Attachment: Bug 2027637 - Update smartbar telemetry events

Comment 3

[Florian Zia [:flozia]]

Attachment: Bug 2027637 - Add extra_key window to urlbar engagement telemetry r=mak,mbeier

Adds the extra_key window to the urlbar engagement telemetry. The key makes it possible to distinguish telemetry between different window modes.

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/9be95dbc6edc
https://hg.mozilla.org/integration/autoland/rev/dce45ee988c1
Update smartbar telemetry events r=urlbar-reviewers,ai-frontend-reviewers,Mardak,daisuke
https://github.com/mozilla-firefox/firefox/commit/9d33901e28ee
https://hg.mozilla.org/integration/autoland/rev/d149e0736cdb
Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/6dc2bbaa39f9
https://hg.mozilla.org/integration/autoland/rev/47eadf23c78d
Revert "Bug 2027637 - Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak" for causing bc failures at engagementTelemtry

Comment 7

[Silaghi Andreea]

Backed out for causing bc and TV failures at engagementTelemetry
Backout Link
Push with failures
Failure Log Bc
Failure log TV
Failure line TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_engagement_window.js | handoff - Test timed out

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/29629d107135
https://hg.mozilla.org/integration/autoland/rev/1c39c19c9289
Update smartbar telemetry events r=urlbar-reviewers,ai-frontend-reviewers,Mardak,daisuke
https://github.com/mozilla-firefox/firefox/commit/1799a1ec61ca
https://hg.mozilla.org/integration/autoland/rev/a571cabdfb5b
Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/0bbd6507ad0f
https://hg.mozilla.org/integration/autoland/rev/255933389dea
Revert "Bug 2027637 - Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak" for causing bc process crashes @ browser_aiwindow_smartbar_telemetry.js

Comment 10

[Sandor Molnar[:smolnar]]

Backed out for causing bc process crashes @ browser_aiwindow_smartbar_telemetry.js

Backout link: https://hg.mozilla.org/integration/autoland/rev/255933389dea46b38f106b79732bb33f61ae4a38

Push with failures

Failure log -> PROCESS-CRASH | 947654f8-8ff1-4039-b6ca-9e6f8888361f | Attempting to connect to non-local address! opener is [chrome://browser/content/tabbrowser/tabbrowser.js:9904:33], uri is [https://www.google.com/search?client=firefox-b-1-d&q=search+for+cats] [@ mozilla::net::nsHttpChannel::OnStartRequest] | browser/components/aiwindow/ui/test/browser/browser_aiwindow_smartbar_telemetry.js

Comment 11

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/eba539b3ac58
https://hg.mozilla.org/integration/autoland/rev/0a2096561973
Update smartbar telemetry events r=urlbar-reviewers,ai-frontend-reviewers,Mardak,daisuke
https://github.com/mozilla-firefox/firefox/commit/9e9afcad2e89
https://hg.mozilla.org/integration/autoland/rev/bcabbb26fe8e
Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak

Comment 12

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/e4967a12f4d9
https://hg.mozilla.org/integration/autoland/rev/b5870abd15c2
Revert "Bug 2027637 - Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak" for causing documentation failures

Comment 13

[Sandor Molnar[:smolnar]]

Backed out for causing documentation failures

Backout link: https://hg.mozilla.org/integration/autoland/rev/b5870abd15c29697c69789caad68cad719f634e4

Push with failures

Failure log -> sphinx.errors.ExtensionError: Handler <function analyze at 0x7f32341aad40> for event 'builder-inited' threw an exception (exception: Your code contains multiple documented objects at each of these paths:

Comment 14

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/ebb9370546c5
https://hg.mozilla.org/integration/autoland/rev/3c465482a379
Update smartbar telemetry events r=urlbar-reviewers,ai-frontend-reviewers,Mardak,daisuke
https://github.com/mozilla-firefox/firefox/commit/d9df5be17087
https://hg.mozilla.org/integration/autoland/rev/7bdee5ba7c96
Add extra_key window to urlbar engagement telemetry r=urlbar-reviewers,ai-frontend-reviewers,daisuke,Mardak

Comment 15

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/3c465482a379
https://hg.mozilla.org/mozilla-central/rev/7bdee5ba7c96

Comment 16

[Florian Zia [:flozia]]

Needs QA from @rdoghi in Nightly Fx151 before uplifting to beta. The two Phabricator revisions associated with this bug also resolve bug 2028783.

Comment 17

[Ciprian Georgiu, Desktop QA]

Florian, I took a look at this patch while Rares is on PTO. It seems that with the latest Nightly 151.0a1 on macOS 26, the telemetry events that were problematic are triggered in about:glean. However, I have some questions that need clarification:

1. For the chatSubmit event, I don't see the value added for memories, although I have memories saved in about:preferences#manageMemories, and they were mentioned a couple of times in the sidebar chat when using the AI. Do we need to have a value for memories as well?
2. The chatSubmit event does not show information when searched from the URL bar under the "location" value. I can only see "fullpage" or "sidebar".
   e.g. { "chat_id": "9e79aae4-8928-4bdf-8607-4feaf4e0ed71", "detected_intent": "chat", "length": "18", "location": "sidebar", "mentions": "0", "message_seq": "0", "model": "Qwen3-235B-A22B-Instruct-2507", "submit_type": "enter", "tabs": "1" }
3. As mentioned in comment 0, "Tabs preselected will not record 1, only if 2 or more are preselected, in which case for 2 tabs added it will show 1 preselected tab (not sure if it's OK; technically it's true if we already add 1 tab, 1 is already there preselected.)". Can you please confirm if this is expected? I can see this behavior on the latest Nightly.
4. Also, from comment 0, "message_seq": does this count the user's prompts as well? For 1 user prompt and 1 response from the AI, it's counted as 2 message_seq. Can you tell us more about how this works? I can see "message_seq": "5" when chatting a bit with the AI.

Comment 18

[Florian Zia [:flozia]]

Thank you @cgeorgiu!

1. Memories are being recorded as part of the chatSubmit event anymore and were removed from the list directly, but can be merged with the model_request telemetry.
2. We did not add the location property to the existing urlbar implemetation and will be covered under bug 2024631. For the purpose of the Smart Window events we can correctly assume that a missing location extra_key means the event comes from the urlbar still.
3. That is the correct behaviour.
4. This is the correct behaviour as well: We are counting user and system prompts.

Comment 19

[Florian Zia [:flozia]]

[removed duplicate comment]

Comment 20

[Ciprian Georgiu, Desktop QA]

(In reply to Florian Zia [:flozia] from comment #18)

Thank you @cgeorgiu!

1. Memories are being recorded as part of the chatSubmit event anymore and were removed from the list directly, but can be merged with the model_request telemetry.
2. We did not add the location property to the existing urlbar implemetation and will be covered under bug 2024631. For the purpose of the Smart Window events we can correctly assume that a missing location extra_key means the event comes from the urlbar still.
3. That is the correct behaviour.
4. This is the correct behaviour as well: We are counting user and system prompts.

Thank you! I'm going to mark this issue verified as fixed on latest Nightly 151.0a1.

I’m also confirming the fix for Bug 2028783. The window_mode key for the urlbar.engagement and urlbar.abandonment events is now correctly displaying classic, private, and Smart Window when following the steps mentioned on Slack.

For urlbar.engagement:

1. Open a window
2. Click in the URL bar
3. Type something: For example “test”
4. Press Enter to navigate or select a result

For urlbar.abandonment:

1. Open a window
2. Click in the URL bar
3. Type something
4. Click away or press Escape without selecting anything