Intent to Implement and Ship: PerformanceObserver.supportedEntryTypes
n...@chromium.org
Contact emails
Spec
https://w3c.github.io/performance-timeline/#supportedentrytypes-attribute
TAG review process is being skipped because this is a small addition to an existing API.
Summary
PerformanceObserver.supportedEntryTypes provides an easy way to feature detect the entry types that are implemented in a web browser. It also allows developers to discover new entry types. The list is returned in alphabetical order. For example, in Chrome, you could get [‘longtask’, ‘mark’, ‘measure’, ‘navigation’, ‘paint’, ‘resource’, ‘taskattribution’].
Motivation
We’d like to make feature detection less hacky. supportedEntryTypes also provides discoverability. See https://github.com/w3c/performance-timeline/issues/77
Risks
Interoperability and Compatibility
Based on https://docs.google.com/document/d/e/2PACX-1vRdJ0Infp2HBESEk2v_1-2kJAEehQkgExlwJTrqxqrvisx8XLAGRYWQiCBHXXqBDCyl2cNp03rsU09g/pub#h.ez8q3dhgycc and pull request https://github.com/w3c/performance-timeline/pull/108:
Edge: Cautious support
Firefox: Cautious support
Safari: Cautious support - suggested doing PerformanceObserver.supports(type). We did not go with this option because it does not provide discoverability.
Web / Framework developers: support.
Ergonomics
There are ergonomics improvements since it allows easy feature detection.
Activation
It can be easily used via Javascript.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Debuggability
Easy debuggability: PerformanceObserver.supportedEntryTypes in Javascript.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
I’m doing WPT tests and the implementation in the same CL.
Entry on the feature dashboard
https://www.chromestatus.com/feature/6737857909620736
Requesting approval to ship?
Yes.
Daniel Bratell
--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/240e82f9-e24a-4800-a1a3-6dce832ff558%40chromium.org.
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.ztieeqo9rbppqq%40cicero2.linkoping.osa.
Mike West
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-nKXakd9QJMo9DJ9UMy%3DZd7_MCWSLvyMPHJLOY3NkV1Q%40mail.gmail.com.
Joe Medley
Nicolás Peña
Boris Zbarsky
> TAG review process is being skipped because this is a small addition to
> an existing API.
the third bullet point of
<https://w3ctag.github.io/design-principles/#attributes-like-data>.
If the TAG review process is going to be skipped, may suggest at least
comparing what change is being proposed to that document in the future?
-Boris
n...@chromium.org
Boris Zbarsky
> I'll send a PR to modify the description of the attribute getter so it
> does not return a new copy every time, and will change Chrome
> implementation accordingly.
-Boris