Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upPerformanceResourceTiming: connectStart #21261
Comments
|
Hi! If you have any questions regarding this issue, feel free to make a comment here, or ask it in the If you intend to work on this issue, then add |
|
@highfive: assign me |
|
Hey @VishalCR7! Thanks for your interest in working on this issue. It's now assigned to you! |
|
@jdm : Hey! I m just getting started. Can you please explain what needs to be done and which files to look at for solving this bug. Thanks in advance :) |
|
Since I don't believe we can determine if a persistent connection is used or not right now, we should set connectStart in the |
|
@highfive: assign me |
|
Hey @nehalem501! Thanks for your interest in working on this issue. It's now assigned to you! |
Implement connectStart in PerformanceResourceTiming <!-- Please describe your changes on the following line: --> - Added connectStart where needed (```ResourceFetchTiming```, ```ResourceAttribute```) in ```components/net_traits/lib.rs ``` - Before calling ```client.request``` in ```obtain_response```, we now add the ```connectStart``` attribute (```components/net/http_loader.rs```) - Updated tests to reflect those changes --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [X] These changes fix #21261 (at least partially) <!-- Either: --> - [X] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23323) <!-- Reviewable:end -->
Implement connectStart in PerformanceResourceTiming <!-- Please describe your changes on the following line: --> - Added connectStart where needed (```ResourceFetchTiming```, ```ResourceAttribute```) in ```components/net_traits/lib.rs ``` - Before calling ```client.request``` in ```obtain_response```, we now add the ```connectStart``` attribute (```components/net/http_loader.rs```) - Updated tests to reflect those changes --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [X] These changes fix #21261 (at least partially) <!-- Either: --> - [X] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23323) <!-- Reviewable:end -->
|
In #23323 it says that this was only fixed partially. Is there more to do here? |
|
Support for persistent connections doesn't exist yet, but we should file a new issue about that. |
If a persistent connection is used, connect_start will be set in components/net/http_loader.rs::http_fetch, otherwise, it will be in components/net/http_loader.rs::obtain_response
On getting, the connectStart attribute MUST return as follows:
https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-connectstart