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

Perf timing dom props #7242

Merged
merged 1 commit into from Nov 14, 2015
Merged

Perf timing dom props #7242

merged 1 commit into from Nov 14, 2015

Conversation

@g-k
Copy link
Contributor

g-k commented Aug 16, 2015

I think this is closer to what #7045 describes, but it panics trying to load a page (trace: https://gist.github.com/g-k/a9911467889cdb6fdbf9) and all reftests fail.

Review on Reviewable

@Ms2ger Ms2ger self-assigned this Aug 17, 2015
@Ms2ger
Copy link
Contributor

Ms2ger commented Aug 17, 2015

The issue is the set_ready_state call in Document::new(), which happens before we've had a chance to hook up the window.

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 16979d7 to e68cd45 Aug 19, 2015
@g-k
Copy link
Contributor Author

g-k commented Aug 19, 2015

Ah! That makes sense. I removed that call and it fixed the panics, but I'm not sure where to set the loading time. Should I add a call to set_ready_state after all Document::new calls or is there a cleaner way to do that?

@Ms2ger
Copy link
Contributor

Ms2ger commented Aug 20, 2015

I've looked at this for a bit, but the specs are a mess; I'm not quite sure what's the best approach here.

@bors-servo
Copy link
Contributor

bors-servo commented Aug 20, 2015

The latest upstream changes (presumably #7265) made this pull request unmergeable. Please resolve the merge conflicts.

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch 2 times, most recently from b726f86 to 53fb7f0 Aug 24, 2015
@bors-servo
Copy link
Contributor

bors-servo commented Aug 27, 2015

The latest upstream changes (presumably #7401) made this pull request unmergeable. Please resolve the merge conflicts.

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 53fb7f0 to f64fd44 Aug 29, 2015
@jdm jdm removed the S-needs-rebase label Aug 30, 2015
@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 5b06cc9 to a88ef97 Sep 6, 2015
@bors-servo
Copy link
Contributor

bors-servo commented Sep 8, 2015

The latest upstream changes (presumably #7561) made this pull request unmergeable. Please resolve the merge conflicts.

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from a88ef97 to b1c0a01 Sep 26, 2015
@g-k
Copy link
Contributor Author

g-k commented Sep 28, 2015

r? @Ms2ger

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 4057f9c to c195e28 Oct 9, 2015
@Manishearth
Copy link
Member

Manishearth commented Oct 13, 2015

@Ms2ger updates?

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from c195e28 to 6c3d287 Oct 23, 2015
@bors-servo
Copy link
Contributor

bors-servo commented Oct 26, 2015

The latest upstream changes (presumably #8094) made this pull request unmergeable. Please resolve the merge conflicts.

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 6c3d287 to c6cff46 Oct 31, 2015
@g-k
Copy link
Contributor Author

g-k commented Nov 1, 2015

I think this is ready for another look.

I rebased and changed the performance timing constructor to take Root<Document> instead of JS<Document> to satisfy the unrooted_must_root lint check.

@jdm jdm assigned jdm and unassigned Ms2ger Nov 11, 2015
@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 144a754 to ee6ca42 Nov 12, 2015
@jdm
Copy link
Member

jdm commented Nov 12, 2015

Looks great! One last piece of cleanup and this will be ready to go. Please squash all the commits into one, too!
-S-awaiting-review +S-needs-squash


Reviewed 1 of 3 files at r1, 1 of 1 files at r7, 1 of 2 files at r8, 1 of 1 files at r9, 3 of 3 files at r10, 1 of 1 files at r11.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.


components/script/dom/document.rs, line 518 [r11] (raw file):
Let's add a update_with_current_time(marker: &Cell<u64>) function that does this check and updates the value, then call that from each place in these methods that duplicates this logic.


Comments from the review on Reviewable.io

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from ee6ca42 to 3891a42 Nov 13, 2015
@jdm
Copy link
Member

jdm commented Nov 13, 2015

Only one question left about the spec link changes!
-S-awaiting-review -S-needs-squash +S-needs-code-changes


Reviewed 3 of 3 files at r12.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


components/script/dom/performancetiming.rs, line 50 [r12] (raw file):
Why this change? Specs under /TR/ are strictly less interesting to us as implementors.


Comments from the review on Reviewable.io

@g-k
Copy link
Contributor Author

g-k commented Nov 13, 2015

Ah, the http://w3c.github.io/ links were 404ing last night. I'll change
them back.

On Fri, Nov 13, 2015 at 2:49 PM, Josh Matthews notifications@github.com
wrote:

Only one question left about the spec link changes!

-S-awaiting-review -S-needs-squash +S-needs-code-changes

Reviewed 3 of 3 files at r12.
Review status: all files reviewed at latest revision, 1 unresolved

discussion.

components/script/dom/performancetiming.rs, line 50 [r12]
https://reviewable.io:443/reviews/servo/servo/7242#-K31O9PAY41SCBFXOpsj

(raw file

// https://www.w3.org/TR/navigation-timing/#dom-performancetiming-navigationstart

):
Why this change? Specs under /TR/ are strictly less interesting to us as

implementors.

Comments from the review on Reviewable.io
https://reviewable.io:443/reviews/servo/servo/7242


Reply to this email directly or view it on GitHub
#7242 (comment).

@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 3891a42 to 66e9be0 Nov 13, 2015
@g-k g-k force-pushed the g-k:perf-timing-dom-props branch from 66e9be0 to e49d592 Nov 13, 2015
@jdm
Copy link
Member

jdm commented Nov 14, 2015

@bors-servo: r+
Thanks!


Reviewed 3 of 3 files at r13.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from the review on Reviewable.io

@bors-servo
Copy link
Contributor

bors-servo commented Nov 14, 2015

📌 Commit e49d592 has been approved by jdm

@bors-servo
Copy link
Contributor

bors-servo commented Nov 14, 2015

Testing commit e49d592 with merge 7de8b0a...

bors-servo added a commit that referenced this pull request Nov 14, 2015
Perf timing dom props

I think this is closer to what #7045 describes, but it panics trying to load a page (trace: https://gist.github.com/g-k/a9911467889cdb6fdbf9) and all reftests fail.

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/7242)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Nov 14, 2015

@bors-servo bors-servo merged commit e49d592 into servo:master Nov 14, 2015
3 checks passed
3 checks passed
code-review/reviewable Review complete: all files reviewed, all discussions resolved
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details
@g-k g-k deleted the g-k:perf-timing-dom-props branch Nov 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

6 participants
You can’t perform that action at this time.