PDF_VIEWER_FALLBACK_REASON should specify that it is only collected in content processes
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: wlach, Assigned: wlach)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Currently it claims to be collected in the main process, but telemetry indicates it is only recorded in the content process.
This can cause confusion:
https://mozilla.slack.com/archives/C4D5ZA91B/p1599738740069900
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Comment 2•4 years ago
|
||
BTW, it looks like there are a number of pdf.js probes that are content only, but marked as both.
Out of curiosity, why do we distinguish between content/main?
|
|
Assignee | |
Comment 4•4 years ago
|
||
(In reply to Brendan Dahl [:bdahl] from comment #2)
BTW, it looks like there are a number of pdf.js probes that are content only, but marked as both.
Oh! If you could file a follow-up bug for those that would be good.
Out of curiosity, why do we distinguish between content/main?
:chutten may be able to say more, but my understanding is that some probes genuinely are accumulated in both the content and main process, and it's useful to distinguish them when doing analysis.
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Description
•