Closed
Bug 1817203
Opened 1 year ago
Closed 1 year ago
Evaluate how we record interactions with the go button
Categories
(Firefox :: Address Bar, defect, P2)
Firefox
Address Bar
Tracking
()
VERIFIED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | verified |
People
(Reporter: mak, Assigned: daisuke)
References
Details
Attachments
(1 file)
I can reproduce some strange events recording when:
1: type something in urlbar
2: selects a one off button with the keyboard
3: click on the Go button
Apart from checking the returned events are consistent, we should probably have a special go_button engagement_type for the go button?
|
Assignee | |
Updated•1 year ago
|
Assignee: nobody → daisuke
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•1 year ago
|
||
Pushed by dakatsuka.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/537373c4625f Introduce go_button in engagement_type r=mak
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
|
||
Comment 4•1 year ago
|
||
The issue is verified fixed in the latest Fx 112.0a1 on Windows 10 and Ubuntu 20.04. The engagement type is now listed as "go_button" using the steps provided in comment 1.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•