| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
// as is the case by default in aw_tracing_controller.ccDoes this require changes to aw_tracing_controller.cc? Is this related to https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/tracing/aw_tracing_controller.cc;l=88;drc=1df1c1323290afd34f4e594be0f54beb2ee5968d or is this referring to a different filter?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// as is the case by default in aw_tracing_controller.ccDoes this require changes to aw_tracing_controller.cc? Is this related to https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/tracing/aw_tracing_controller.cc;l=88;drc=1df1c1323290afd34f4e594be0f54beb2ee5968d or is this referring to a different filter?
So apparently TracingController is a public API on webview:
https://developer.android.com/reference/android/webkit/TracingController#start(android.webkit.TracingConfig)
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
Removing this would expose a lot more things - I don't know if it makes sense to do so, but the current allowlist doesn't make a lot of sense either. Thoughts?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// as is the case by default in aw_tracing_controller.ccEtienne Pierre-DorayDoes this require changes to aw_tracing_controller.cc? Is this related to https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/tracing/aw_tracing_controller.cc;l=88;drc=1df1c1323290afd34f4e594be0f54beb2ee5968d or is this referring to a different filter?
So apparently TracingController is a public API on webview:
https://developer.android.com/reference/android/webkit/TracingController#start(android.webkit.TracingConfig)
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
Removing this would expose a lot more things - I don't know if it makes sense to do so, but the current allowlist doesn't make a lot of sense either. Thoughts?
We discussed offline, but is it possible to separate out the chrome change from the WebView change? If so, then I'd like to see if we can put the WebView behavior behind a base::Feature flag to allow us a more cautious rollout.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// as is the case by default in aw_tracing_controller.ccEtienne Pierre-DorayDoes this require changes to aw_tracing_controller.cc? Is this related to https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/tracing/aw_tracing_controller.cc;l=88;drc=1df1c1323290afd34f4e594be0f54beb2ee5968d or is this referring to a different filter?
Nate FischerSo apparently TracingController is a public API on webview:
https://developer.android.com/reference/android/webkit/TracingController#start(android.webkit.TracingConfig)
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
Removing this would expose a lot more things - I don't know if it makes sense to do so, but the current allowlist doesn't make a lot of sense either. Thoughts?
We discussed offline, but is it possible to separate out the chrome change from the WebView change? If so, then I'd like to see if we can put the WebView behavior behind a base::Feature flag to allow us a more cautious rollout.
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
This wasn't quite true, trace events are still emitted, but with no arguments.
Still, doing this will now expose all protos that are privacy reviewed - the same one could get through devtools API.
I added Android.WebView.ApiCall.TracingController which shows this API is mostly unused - O(10) API calls - probably only for local debuging.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
// as is the case by default in aw_tracing_controller.ccEtienne Pierre-DorayDoes this require changes to aw_tracing_controller.cc? Is this related to https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/tracing/aw_tracing_controller.cc;l=88;drc=1df1c1323290afd34f4e594be0f54beb2ee5968d or is this referring to a different filter?
Nate FischerSo apparently TracingController is a public API on webview:
https://developer.android.com/reference/android/webkit/TracingController#start(android.webkit.TracingConfig)
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
Removing this would expose a lot more things - I don't know if it makes sense to do so, but the current allowlist doesn't make a lot of sense either. Thoughts?
Etienne Pierre-DorayWe discussed offline, but is it possible to separate out the chrome change from the WebView change? If so, then I'd like to see if we can put the WebView behavior behind a base::Feature flag to allow us a more cautious rollout.
This is a bit silly though, because the allowlist as-is only allows collecting memory-infra (heap dumps).
This wasn't quite true, trace events are still emitted, but with no arguments.
Still, doing this will now expose all protos that are privacy reviewed - the same one could get through devtools API.
I added Android.WebView.ApiCall.TracingController which shows this API is mostly unused - O(10) API calls - probably only for local debuging.
Acknowledged
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[tracing] Remove json allowlist
This CL removes json args allow list.
The allowlist is unnecessary because privacy filters
are now always run before JSON conversion when requested.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |