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

101 views
Skip to the first unread message

Kenji Baheux

unread,
6 Jun 2016, 22:28:5906/06/2016
to blink-dev, ri...@google.com, Ilya Grigorik
ri...@chromium.orgkenji...@chromium.org
  https://w3c.github.io/resource-timing/ Add size related attributes to Resource Timing API Changes to API surface:
  • Add 3 attributes (transfer/encoded/decoded sizes)
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)
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.

Low (not aware of specific concerns from other vendors about these 3 new fields). +Ilya to keep me honest.
None
Yes http://crbug.com/611278 https://www.chromestatus.com/features/6549060404117504 Yes

Yoav Weiss

unread,
7 Jun 2016, 09:33:5207/06/2016
to Kenji Baheux, blink-dev, ri...@google.com, Ilya Grigorik
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

unread,
7 Jun 2016, 11:59:4707/06/2016
to Kenji Baheux, blink-dev, ri...@google.com
On Mon, Jun 6, 2016 at 7:28 PM, Kenji Baheux <kenji...@google.com> wrote:
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.


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

TAMURA, Kent

unread,
7 Jun 2016, 20:39:0107/06/2016
to Kenji Baheux, blink-dev, ri...@google.com, Ilya Grigorik
LGTM1.

--
TAMURA Kent
Software Engineer, Google


Chris Harrelson

unread,
8 Jun 2016, 01:49:2808/06/2016
to TAMURA, Kent, Kenji Baheux, blink-dev, ri...@google.com, Ilya Grigorik
LGTM2

Jochen Eisinger

unread,
8 Jun 2016, 02:00:4508/06/2016
to Chris Harrelson, TAMURA, Kent, Kenji Baheux, blink-dev, ri...@google.com, Ilya Grigorik

lgtm3

senid...@gmail.com

unread,
29 Sept 2016, 04:04:2329/09/2016
to blink-dev, ri...@google.com, igri...@google.com, kenji...@google.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:

PhistucK

unread,
29 Sept 2016, 04:45:0829/09/2016
to senid...@gmail.com, blink-dev, Adam Rice, Ilya Grigorik, Kenji Baheux
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

unread,
29 Sept 2016, 04:52:5029/09/2016
to senid...@gmail.com, blink-dev, Adam Rice, Ilya Grigorik, Kenji Baheux
Also, generally, ChromeStatus has this information -


PhistucK

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

--
Reply all
Reply to author
Forward
0 new messages