Hey Chromium Developers,

tl;dr: For enabling better web platform telemetry, we are requesting
everyone to add/map WebDXFeature use counters for all new web platform
features going forward and for all features shipped since 2020 and
contribute to feature definitions and WPT test mapping.

As briefly shared
<https://www.youtube.com/watch?v=T7Sz0Mwf3ts&list=PL9ioqAuyl6UISoeMLjzTjk2GvxbJ54jqc&index=2&t=543s>
at BlinkOn 19 in early October this year, we're excited to announce a new
initiative to improve the availability of web platform feature telemetry.
This will help the entire community better understand how features we ship
in Chromium based browsers are being adopted, ultimately leading to more
informed decision-making and prioritization for all of us.

What’s needed?

Going forward, we request that all new web platform features include a
WebDXFeature
use counter
<https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/use_counter/metrics/webdx_feature.mojom>,
and we’re actively adding use counters for all features shipped in Chrome
since 2020. This is similar to adding a WebFeature use counter and will
help us track active usage of features. By incorporating these new use
counters, you'll be directly contributing to the collective understanding
of feature adoption across the web. We’re actively working on making this
use counter data publicly available through both webstatus.dev and
chromestatus.com late this year and early in 2025.

WebDXFeature use counters
<https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/use_counter/metrics/webdx_feature.mojom>
are a new type of use counters that provide insights into feature usage
across all channels and platforms for Chrome installs in the wild. Feature
usage is recorded per page load and is anonymously aggregated. The goal is
to have one representative WebDXFeature use counter that maps directly to a
high level feature as defined per the web-features project
<https://github.com/web-platform-dx/web-features>.


   -

   Please add WebDXFeature use counters for all new features (and other
   recent features you own!) shipped since 2020
   -

      You can add them just like you add WebFeature use counters
      -

      If a WebFeature/CSSSampleId counter(s) already exist, map them to the
      new WebDXFeature counter (in use_counter_page_load_metrics_observer.cc
      
<https://source.chromium.org/chromium/chromium/src/+/main:components/page_load_metrics/browser/observers/use_counter_page_load_metrics_observer.cc;l=313>
      )
      -

      Refer to webdx_feature.mojom
      
<https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/use_counter/metrics/webdx_feature.mojom?q=webdx_feature.mojom&ss=chromium%2Fchromium%2Fsrc>
      for naming details
      -

      Tracking bug to add WebDXFeature use counter at crbug.com/366475997
      -

      Use Counter burndown list (now largely complete) at bit.ly/webdxuc
      -

   Please contribute to the feature definitions at
   github.com/web-platform-dx/web-features
   -

   Please contribute to the mapping of WPT tests to your features (see
   WEB_FEATURES.yml files in the WPT repository
   <https://github.com/web-platform-tests/wpt>)
   -

   More detailed information available here
   
<https://docs.google.com/document/d/1iiat-77KuFxEWLqSXvC754LG36H_vcbF5A0Y5bwQzVg/edit?tab=t.0>
   .


Your expertise and insights will be invaluable in creating a comprehensive
and accurate feature map. By working together, we can create a more
transparent and data-driven web development ecosystem, benefiting
developers, browser vendors, and end-users alike.

Thank you for your contributions,

Johnny, on behalf of the Chrome Web Platform Team

-- 
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 blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz7yLQpnpmZqyFv94JaZN0KOCPRWHpFLZ6f%2BEe2hc3gwgw%40mail.gmail.com.

Reply via email to