Multiple “Invalid” Event reports generated in the Console after restarting Firefox Enterprise
Categories
(Enterprise Products :: Console, defect)
Tracking
(Not tracked)
People
(Reporter: sbadau, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Found in
Affected versions
Tested platforms
- Affected platforms: Windows 11 x64, Ubuntu 24.04 and macOS 26
Preconditions
- Firefox Enterprise is installed and a user is authenticated.
- A Company admin is logged into the Console.
Steps to reproduce
- In Firefox Enterprise - access a blocked domain and then Restart the browser (Ctrl+Shift+J followed by Ctrl+Alt+R)
- Go to the Console and check the Event reports.
Expected result
- Event Reports should only be generated for valid, monitored user actions.
Actual result
- Approximately 15 Invalid Event Reports are generated simply from restarting the browser (all the reports above the "Blocklist domain browsed" one)
Regression range
- this is not a regression.
Comment 1•8 months ago
|
||
I think the invalid events are now filtered. Can you check now?
Thanks :)
| Reporter | ||
Comment 2•8 months ago
|
||
When looking at the console, I don’t see any invalid report events being generated. However, at the time of writing this comment, no new events are being generated for me.
I'm using the GCP-EU console with Firefox Enterprise 148.0a1 (Build ID: 20251223172112) installed from the GitHub Merge.
@Julien, if the absence of new events is related to this Firefox Enterprise build not being the appropriate one, could you please direct me to the correct build I should use for testing?
Comment 3•8 months ago
|
||
Ah, I don't know :-( better ask on Slack about this
Comment 4•7 months ago
|
||
Hey Simona, have you managed to verify this after all?
| Reporter | ||
Comment 5•7 months ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #4)
Hey Simona, have you managed to verify this after all?
Yes, I haven't seen the invalid events being generated during the last testing session.
Comment 6•7 months ago
|
||
Thank you, then I consider this is fixed :-)
Comment 7•6 months ago
|
||
Verified fixed on the 149.0a1 version (Build ID:20260221191449) during Alpha test run 1 on https://stage.fx-enterprise.nonprod.webservices.mozgcp.net/event-reports
Comment 8•6 months ago
|
||
Description
•