diff options
author | bors-servo <lbergstrom+bors@mozilla.com> | 2017-08-17 12:27:19 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-08-17 12:27:19 -0500 |
commit | 6988c7424ddfdd9a98e6a458ff2ad307a74237aa (patch) | |
tree | 6725b4cf17157fcec74f0c4a327394f563a01a91 /components/layout_thread | |
parent | cc86ca2bcdec5e89ee5279085ea38db63ef41af9 (diff) | |
parent | 52348f1fccea3e4abc2ad80d001a43f5f51cbdc8 (diff) | |
download | servo-6988c7424ddfdd9a98e6a458ff2ad307a74237aa.tar.gz servo-6988c7424ddfdd9a98e6a458ff2ad307a74237aa.zip |
Auto merge of #18028 - ferjm:performance.timeline, r=jdm
Performance Timeline API
[Performance Timeline API](https://www.w3.org/TR/performance-timeline-2/) implementation.
This API is required to allow DOM access to the [Paint Timing API](https://wicg.github.io/paint-timing/#example) metrics implemented in #17256. Unfortunately, I couldn't test it properly, as its usage depends on other APIs like the Paint Timing, User Timing, Resource Timing or Server Timing APIs. I'll work in the integration with the Paint Timing API next.
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [ ] There are [WPTs](https://github.com/servo/servo/tree/master/tests/wpt/web-platform-tests/performance-timeline) for this API, however they depend on the implementation of the User Timing and the Resource Timing APIs, which I'll hopefully be implementing soon.
<!-- 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/18028)
<!-- Reviewable:end -->
Diffstat (limited to 'components/layout_thread')
0 files changed, 0 insertions, 0 deletions