Closed Bug 2027638 Opened 5 months ago Closed 5 months ago

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

Categories

(Core :: Machine Learning: Frontend, defect)

Desktop
Unspecified
defect

Tracking

()

RESOLVED DUPLICATE of bug 2027637
Tracking Status
firefox-esr140 --- disabled
firefox149 --- disabled
firefox150 --- affected
firefox151 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [genai][input])

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

Status: NEW → RESOLVED
Closed: 5 months ago
Duplicate of bug: 2027637
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.