Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix resource-timing.https.html test #10905

Merged
merged 1 commit into from
May 8, 2018

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented May 8, 2018

This CL changes resource-timing-worker.js to use a generated response.
This means Chrome no longer passes the test.

Change-Id: Ib983e4fba9e81ddbee7f9572b6a06b3c1825577a
Reviewed-on: https://chromium-review.googlesource.com/1050383
Commit-Queue: Nicolás Peña Moreno npm@chromium.org
Reviewed-by: Timothy Dresser tdresser@chromium.org
Cr-Commit-Position: refs/heads/master@{#556964}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1050383 branch 2 times, most recently from 6e8ce4d to 6706598 Compare May 8, 2018 20:39
This CL changes resource-timing-worker.js to use a generated response.
This means Chrome no longer passes the test.

Change-Id: Ib983e4fba9e81ddbee7f9572b6a06b3c1825577a
Reviewed-on: https://chromium-review.googlesource.com/1050383
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556964}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants