Server Timing entries should be empty array for cross-origin resources |
||||
Issue descriptionAccording to the spec here (https://w3c.github.io/server-timing/#processing-model) cross origin resources should return an empty array for `serverTiming`. Today, unfortunately, they return an array of "zero-ed" out entries (duration=0, description=<empty string>). The name of each entry leaks out, which was correct in an outdated version of the spec, but is no longer correct today.
,
Jan 19 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2cd5223064b2dd0a4800f7b59da932246cd6fb18 commit 2cd5223064b2dd0a4800f7b59da932246cd6fb18 Author: Charles Vazac <cvazac@akamai.com> Date: Fri Jan 19 21:51:04 2018 Fix ServerTiming results for resources that fail TAO check Per spec (https://w3c.github.io/server-timing/#processing-model), resources that fail the TAO check should return an empty array for the serverTiming attribute. Bug: 802321 Change-Id: I0bca0f38f0a975f7c85f4d8837a901bd8475d9b7 Reviewed-on: https://chromium-review.googlesource.com/870990 Commit-Queue: Yoav Weiss <yoav@yoav.ws> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Cr-Commit-Position: refs/heads/master@{#530622} [add] https://crrev.com/2cd5223064b2dd0a4800f7b59da932246cd6fb18/third_party/WebKit/LayoutTests/external/wpt/server-timing/cross_origin.html [modify] https://crrev.com/2cd5223064b2dd0a4800f7b59da932246cd6fb18/third_party/WebKit/Source/core/timing/Performance.cpp [modify] https://crrev.com/2cd5223064b2dd0a4800f7b59da932246cd6fb18/third_party/WebKit/Source/core/timing/PerformanceBase.cpp [modify] https://crrev.com/2cd5223064b2dd0a4800f7b59da932246cd6fb18/third_party/WebKit/Source/core/timing/PerformanceServerTiming.cpp [modify] https://crrev.com/2cd5223064b2dd0a4800f7b59da932246cd6fb18/third_party/WebKit/Source/core/timing/PerformanceServerTiming.h
,
Feb 28 2018
Should this be marked Fixed?
,
Feb 28 2018
,
Apr 3 2018
,
Apr 3 2018
Pls apply appropriate OSs label. FYI: At the point we're not planning any further M65 releases for Chrome Desktop and Chrome Mobile.
,
Apr 4 2018
,
Apr 12 2018
We're not planning any further M65 releases. So rejecting merge to M65. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Jan 16 2018