Improve Cache API's exposure of what it's doing to the Firefox Profiler by clearly expressing the origin it's associated with and distinguishing content usage from QM init sweeps or data-clearing API requests
Categories
(Core :: Storage: Cache API, enhancement, P3)
Tracking
()
People
(Reporter: asuth, Unassigned)
References
Details
We could do a better job of exposing what Cache API threads are getting up to at a high level to the Firefox Profiler. In particular, bug 1759708 is an example of where the opacity of what a thread is doing can make it ambiguous if the Cache API is doing something like a QM init sweep or a Sanitizer.sys.mjs-related thing or if it's doing something on the behalf of an origin, and what origin it's doing it on behalf of in the first place. That said, we should make sure that when exposing the origin that the profiler's upload sanitization mechanism 1) works correctly, but that 2) we can distinguish web-extension origins from content origins from system origins.
When pursuing this, it could also make sense to see if we can also improve our exposure to about:processes at the same time, but we should use a separate bug for anything particularly involved.
Description
•