tracing: add a metadata event to distinguish chrome from webview |
||||||
Issue descriptionSee discussion in https://github.com/catapult-project/catapult/issues/2119#issuecomment-211917655 I think we need a metadata event to tell without ambiguity the browser type. One alternative could be leverage the knowledge that webview is in-process and it has a CrRendererMain. But that is fragile because: - Other single-process-mode things might end up being confused with webview. - In future WebView might become multi process, so bummer. Let's just have a civilized and explicit solution for this.
,
Oct 5 2016
,
Nov 25 2016
,
Feb 10 2017
,
Feb 10 2017
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by petrcermak@chromium.org
, Oct 5 2016