Fix `pocket.click` and `topsite.click` missing context menu triggers
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox160 | --- | fixed |
People
(Reporter: joelkelly, Assigned: joelkelly, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [hnt][hnt-journeys])
Attachments
(1 external file)
Both events fail to fire for:
- right click -> new tab, new window, new private window
- open content/topsite menu -> new private window
Also add a background extra and update event_source to capture these cases accurately.
Consume the notification added in bug 2061813. The tile is resolved from
store state by its url and the click is routed back through the ordinary
click handlers, so a context menu click cannot drift from a plain one.
Also record the private window item in newtab's own menu, which was left
switched off behind a TODO. Both cases are ordinary clicks on an ordinary
newtab in an ordinary session; nothing about the private window is recorded.
The private window option carried almost none of the tile data the new window
option does, so give it the same payload.
Add a background extra to both events and an event_source to topsites.click,
which had neither, and correct the click descriptions: they claimed context
menu opens were not recorded.
background is stripped from the newtab-content ping. Only context menu opens
set it, so keeping it would say how a link was opened on the ping that strips
event_source precisely to avoid that.
handleTopSitesOrganicImpressionStats stringified smart scores unconditionally.
Content always sends them so it never showed, but tiles resolved here need not
have any, and Glean rejects the undefined that JSON.stringify returns.
Comment 2•2 months ago
|
||
The severity field is not set for this bug.
:thecount, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 5•1 month ago
|
||
Reverted this because it was causing mochitests failures in browser_context_menu_link_open.js.
- Revert link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/extensions/newtab/test/browser/browser_context_menu_link_open.js | test_open_link_in_tab_notifies - Recorded 1 topsites.click - Got +0, expected 1
Updated•12 days ago
|
Description
•