Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
NoneIntent to ship roughly by the end of 2025, in M145.
Contact emailsniko...@chromium.orgExplainerhttps://github.com/explainers-by-googlers/cpu-performanceSpecificationNoneSummaryExpose some information about how powerful the user device is. This API targets web applications that will use this information to provide an improved user experience, possibly in combination with the Compute Pressure API, which provides information about the user device’s CPU pressure/utilization and allows applications to react to changes in CPU pressure.Blink componentBlink>PerformanceAPIsWeb Feature IDMissing featureMotivationAt present, some video conferencing applications support advanced functionality by relying on internal/private browser extensions or APIs to classify devices into performance categories. Our proposal allows these applications to support existing functionality without depending on such non-standard features. Applications whose functionality depends on client-side hardware detection often resort to running benchmark workloads, to estimate hardware capabilities. Providing a public CPU Performance API would help prevent a needless waste of resources.Initial public proposalhttps://github.com/explainers-by-googlers/cpu-performanceTAG reviewNoneTAG review statusPending
--
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+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMHN%3DHydj6Q7pz6i_y3j1ON20a270NFGx%2BKD11Q3VdfTXvtCDg%40mail.gmail.com.