Intent to implement and ship: size related attributes for Resource Timing API

[Kenji Baheux]

Contact emails ri...@chromium.org, kenji...@chromium.org

  Spec https://w3c.github.io/resource-timing/ Summary Add size related attributes to Resource Timing API Changes to API surface:

• Add 3 attributes (transfer/encoded/decoded sizes)
  

Motivation These 3 attributes gives developers extra insights about data consumption and performance.

Some sample use cases that come to mind:

• get an accurate understanding of the cache hit rate for key assets
  
• measure bandwidth consumption (and ultimately enforce budgets)

Interoperability risk Firefox: Shipped.

Edge: No public signals but...

• Edge already has a strong implementation of Resource Timing API
  
• And we know that the Edge team is aware and understand the developer enthusiasm for these additions.

Safari: No public signals.

Web developers: Positive.

Compatibility risk Low (not aware of specific concerns from other vendors about these 3 new fields). +Ilya to keep me honest.

Ongoing technical constraints None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes OWP launch tracking bug http://crbug.com/611278 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/6549060404117504 Requesting approval to ship? Yes

[Yoav Weiss]

non-API-owner LGTM!!!11 \o/

Glad to see this implemented. I'll be happy to help with reviews if needed.

--
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.

[Ilya Grigorik]

On Mon, Jun 6, 2016 at 7:28 PM, Kenji Baheux <kenji...@google.com> wrote:

Compatibility risk Low (not aware of specific concerns from other vendors about these 3 new fields). +Ilya to keep me honest.

Yep, not aware of any issues here; we should be good to go!

Also, before the question comes up, access to these attributes is controlled by the same TAO mechanism [1] as other Resource Timing metrics - i.e. third parties have to opt-in via the Timing-Allow-Origin response header for the size attributes to return non zero values.

[1] http://w3c.github.io/resource-timing/#cross-origin-resources

p.s. woohoo, super excited about this work!!

[TAMURA, Kent]

LGTM1.

--

TAMURA Kent
Software Engineer, Google

[Chris Harrelson]

LGTM2

[Jochen Eisinger]

lgtm3

[senid...@gmail.com]

Hi,

are these attributes shipped already with any chrome version?. is it available in Version 53.0.2785.116 m ?

On Monday, 6 June 2016 19:28:59 UTC-7, Kenji Baheux wrote:

Contact emails ri...@chromium.org, kenjibaheux...@chromium.org

[PhistucK]

Chrome 54 beta has them, see the blog post.

☆PhistucK

--

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+unsubscribe@chromium.org.

[PhistucK]

Also, generally, ChromeStatus has this information -

https://www.chromestatus.com/features/6549060404117504

☆PhistucK

On Thu, Sep 29, 2016 at 11:04 AM, <senid...@gmail.com> wrote:

--