We have some instances where we have JS markers from the platform that aren't actionable or make any sense to a web developer, like "nsGlobalWindow report new global" when a debugger instance is wired up. We should hide these behind a `isPlatform` field on ProfileTimelineMarker, and still display them, but obfuscate the name unless Show Platform Data is on (similar to what we do for the call tree, in showing how it impacted performance, but hide names behind general categories)

I think this should be done at the devtools config level, rather than the platform level (it isn't clear to me, which you are proposing).

I think I'd prefer it on the platform level (as part of ProfileTimelineMarker itself), in the case where the "reasons" change on the platform

(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #2) > I think I'd prefer it on the platform level (as part of > ProfileTimelineMarker itself), in the case where the "reasons" change on the > platform Whether or not the marker is shown is a UI concern, not really a platform concern IMO.

That is true -- I just worry about getting out of sync with marker name changes, but realistically that shouldn't happen often.

Handling this in bug 1166005 on the client