New issue
Advanced search Search tips

Issue 799843 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
panicker@chromium.org
igrigo...@chromium.org
ricea@chromium.org
tdres...@chromium.org
yoavweiss@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Resource Timing secureConnectionStart tests do not pass over HTTPS

Project Member Reported by y...@yoav.ws, Jan 8 2018 
Chrome Version: M65
OS: OSX

What steps will reproduce the problem?
(1) https://w3c-test.org/resource-timing/test_resource_timing.html
(2) https://w3c-test.org/resource-timing/resource-timing.html


What is the expected result?
All tests to pass (as they do in the http version)

What happens instead?
multiple test failures, related to secureConnectionStart

Comment 1 by ricea@chromium.org, Jan 30 2018

Cc: ricea@chromium.org
Labels: Needs-Feedback
If I understand correctly, these tests should not pass over HTTPS. They assert that secureConnectionStart is 0, but over a secure connection secureConnectionStart should be non-zero.

The tests also fail in Firefox.

Comment 2 by y...@yoav.ws, Jan 30 2018

Status: WontFix (was: Untriaged)
Fair enough. I guess that's a problem with the tests (which should change expectations based on the scheme they're accessed on)
►

Sign in to add a comment