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.

Sign up for GitHub

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

Jump to bottom

👽 Updated code to follow the latest spec of Server Timing #10

Merged
merged 1 commit into from
Apr 24, 2017
Merged

👽 Updated code to follow the latest spec of Server Timing #10

merged 1 commit into from
Apr 24, 2017

Conversation

motss
Copy link
Contributor

@motss motss commented Apr 22, 2017

@yosuke-furukawa

To fix #9 .

  • Server Timing now accepts value in milliseconds instead of seconds

@motss
👽 Updated code to follow the latest spec of Server Timing
eaeae06 
Server Timing now accepts value in milliseconds instead of seconds
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling eaeae06 on motss:master into 9805311 on yosuke-furukawa:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling eaeae06 on motss:master into 9805311 on yosuke-furukawa:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling eaeae06 on motss:master into 9805311 on yosuke-furukawa:master.

@yosuke-furukawa
Copy link
Owner

ya ! thank you for your PR. LGTM.

@yosuke-furukawa yosuke-furukawa merged commit 396f4f4 into yosuke-furukawa:master Apr 24, 2017
@motss
Copy link
Contributor Author

motss commented Apr 24, 2017

Thank you. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Question on the server timing on Chrome 58+
3 participants
@motss @coveralls @yosuke-furukawa