Open Bug 1662246 Opened 5 years ago Updated 5 years ago

Differentiate markers that are generated by cloned documents

Categories

(Core :: Gecko Profiler, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: sefeng211, Unassigned)

Details

Our print feature will generate a cloned static document that has the same URI as the original document.

This is problematic when the markers that came from the newly cloned documents go to the profile because there's no way to tell if the markers come from the original document or the newly cloned document.

I think one way to fix this is by adding a new attribute to the marker payload to indicate whether this is from a cloned document or not.

Thank you Sean for filing this.

Profiler markers are officially part of the "Gecko Profiler" 😉 I've just moved the bug in that component. ("Performance Tools" is more for the devtools panel, and about:profiling)
Or in this case, because it's for a specific marker, the bug could instead be in the relevant component corresponding to the domain that the marker documents; up to you if you want to move it there...

Severity: -- → N/A
Component: Performance Tools (Profiler/Timeline) → Gecko Profiler
Priority: -- → P2
Product: DevTools → Core
You need to log in before you can comment on or make changes to this bug.