Skip to content

/ servo

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

Jump to bottom

Set ResourceFetchTiming relative to performance time origin instead of precise_time_ns's epoch #25660

Open
pshaughn opened this issue Jan 31, 2020 · 0 comments
Open

Set ResourceFetchTiming relative to performance time origin instead of precise_time_ns's epoch #25660

pshaughn opened this issue Jan 31, 2020 · 0 comments
Labels
A-perf-measurement

Comments

@pshaughn
Copy link
Member

@pshaughn pshaughn commented Jan 31, 2020

servo/components/net_traits/lib.rs

Lines 543 to 545 in 0bf4703

// TODO currently this is being set with precise time ns when it should be time since
// time origin (as described in Performance::now)
pub fn set_attribute(&mut self, attribute: ResourceAttribute) {

There might not be test coverage for this yet.
@pshaughn pshaughn changed the title Set ResourceFetchTiming relative to performance time origin instead of epoch Set ResourceFetchTiming relative to performance time origin instead of precise_time_ns's epoch Jan 31, 2020
@jdm jdm added this to To do in web-platform-test failures via automation Jan 31, 2020
@jdm jdm removed this from To do in web-platform-test failures Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-perf-measurement
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@jdm @pshaughn
You can’t perform that action at this time.