Contact emails [email protected]
Explainer https://github.com/WICG/webrtc-diagnostic-logging/blob/main/explainer.md Specification https://w3c.github.io/webrtc-extensions/#diagnostic-logging Summary The Real-time Communication for the Web ([WebRTC](https://webrtc.org/)) Diagnostic Logging API allows authorized web applications to trigger the collection of WebRTC diagnostic data so that it can be used for local debugging. It also allows an application to share the WebRTC diagnostic data with the user agent vendor, subject to user authorization, with the purpose of providing information that can help fix bugs in or improve the user agent. Admins can enable diagnostic logs with the enterprise policy [WebRtcDiagnosticLogCollectionAllowedForOrigins](https://chromeenterprise.google/policies/#WebRtcDiagnosticLogCollectionAllowedForOrigins). Blink component Blink>WebRTC Web Feature ID webrtc TAG review https://github.com/w3ctag/design-reviews/issues/1250 TAG review status Pending Origin Trial Name WebRTC Diagnostic Logging API Goals for experimentation We want to test to what extent the API properly supports the following use cases: * Allowing enterprises to collect diagnostic data about WebRTC in order to assist in debugging online problems * Collaborate with UA vendors to fix UA WebRTC bugs. Chromium Trial Name RTCDiagnosticLogging Origin Trial documentation link https://github.com/WICG/webrtc-diagnostic-logging/blob/main/explainer.md WebFeature UseCounter name kV8RTC_StartDiagnosticLogging_Method Risks Interoperability and Compatibility No information provided Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1436) Mozilla's representative in the WebRTC WG approved adding this feature to the WebRTC Extensions spec. See https://github.com/w3c/webrtc-extensions/pull/255#issuecomment-5620215770 WebKit: No signal (https://github.com/WebKit/standards-positions/issues/699) Apple's representative in the WebRTC WG approved adding this feature to the WebRTC Extensions spec. See https://github.com/w3c/webrtc-extensions/pull/255#pullrequestreview-5168267473 Web developers: Positive An origin trial partner has expressed positive views. Some developers (bytedance, alcatel/lucent) have expressed interest in the use cases supported by this feature before it was developed, but have not provided direct feedback afterwards. https://github.com/w3c/webrtc-extensions/issues/124 Other signals: Ergonomics N/A Activation N/A WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? N/A Reason this experiment is being extended This API shipped. This request is just to give OT participants more time to migrate to the shipped spec version, which has some differences with the API available during most of the OT. Ongoing technical constraints N/A Debuggability No information provided Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes Supported on desktop platforms. Is this feature fully tested by web-platform-tests? Yes https://crsrc.org/c/third_party/blink/web_tests/wpt_internal/webrtc/ Flag name on about://flags No information provided Finch feature name RTCDiagnosticLogging Requires code in //chrome? True Tracking bug https://crbug.com/481412281 Launch bug https://launch.corp.google.com/launch/4419765 Measurement https://chromestatus.com/metrics/feature/timeline/popularity/5941 Availability expectation Feature is available only in Chromium browsers for the foreseeable future, but has consensus in the W3C WebRTC WG. Adoption expectation Feature is used by specific partner(s) to provide functionality within 12 months of launch in Chrome. Estimated milestones Shipping on desktop 156 Origin trial desktop first 151 Origin trial desktop last 156 Origin trial extension 1 end milestone 162 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5091582546149376?gate=5088531566428160 Links to previous Intent discussions Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a3a6980.3af95f39.2b348.0333.GAE%40google.com Intent to Ship: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6ab69367.6459a8fd.9ebb.013d.GAE%40google.com This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6ad0118b.bcaae8da.1bd4b2.0015.GAE%40google.com.
