New issue
Advanced search Search tips

Issue 630055 link

Starred by 2 users
Status: Fixed
Owner:
ricea@chromium.org
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

PerformanceResourceTiming transferSize field is not set in Workers

Project Member Reported by ricea@chromium.org, Jul 21 2016 
What steps will reproduce the problem?
(1) Perform an uncached load in a Worker
(2) Observe the PerformanceResourceTiming object for the load
(3) Look at the transferSize field

What is the expected output?

Field is non-zero.

What do you see instead?

Field is zero.
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 27 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/147a3f85d9f0bb1e2a654822a555d470f5fa45d4

commit 147a3f85d9f0bb1e2a654822a555d470f5fa45d4
Author: ricea <ricea@chromium.org>
Date: Wed Jul 27 05:21:27 2016

Set Resource Timing transferSize field in Workers

The transferSize field was not correctly set in Worker contexts. Fix it.

Also create variants of the PerformanceResourceTiming size field layout
tests which use a Worker.

The common code between the worker and non-worker tests is factored out into
javascript files.

BUG= 630055 

Review-Url: https://codereview.chromium.org/2159163002
Cr-Commit-Position: refs/heads/master@{#408048}

[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-cache-worker.html
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-cache.html
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-content-encoding-worker.html
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-content-encoding.html
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-cors-preflight-worker.html
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-cors-preflight.html
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-redirect-worker.html
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-redirect.html
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-xhr-fetch-worker.html
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resource-timing-sizes-xhr-fetch.html
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resources/resource-timing-sizes-cache.js
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resources/resource-timing-sizes-content-encoding.js
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resources/resource-timing-sizes-cors-preflight.js
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resources/resource-timing-sizes-redirect.js
[add] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/LayoutTests/http/tests/misc/resources/resource-timing-sizes-xhr-fetch.js
[modify] https://crrev.com/147a3f85d9f0bb1e2a654822a555d470f5fa45d4/third_party/WebKit/Source/platform/network/ResourceTimingInfo.cpp

Comment 2 by ricea@chromium.org, Jul 29 2016

Status: Fixed (was: Started)
►

Sign in to add a comment