Uh oh!
There was an error while loading. Please reload this page.
lib: expose performance interface to global - #32790
Conversation
| exposeInterface(global, 'URLSearchParams', URLSearchParams); | ||
| const { performance } = require('perf_hooks'); | ||
| // https://www.w3.org/TR/performance-timeline/ |
There was a problem hiding this comment.
| // https://www.w3.org/TR/performance-timeline/ | |
| // https://www.w3.org/TR/performance-timeline/ | |
| // https://www.w3.org/TR/hr-time-2/ |
quoting my comments in #28635 (comment)
|
jasnell
commented
May 1, 2020
+1 to what @joyeecheung said. |
targos
left a comment
There was a problem hiding this comment.
This should also expose PerformanceObserver
targos
commented
May 7, 2020
I'm looking at the spec for |
jasnell
commented
May 7, 2020
That depends on the specific pieces you're seeing but the short version is: we're intentionally not fully compliant because the specs written includes a built-in memory leak that we are avoiding. |
targos
commented
May 7, 2020
I don't know what you are referring to, but the first thing I noted is that we support the |
jasnell
commented
May 7, 2020
I could be mistaken but |
juanarbol
commented
May 13, 2020
Performance API seems to need more love (hopefully I could help to stabilize this) and semver major cut was few weeks ago. I better close this PR. |
juanarbol
commented
May 13, 2020
Oh, sorry, I see activity related to this. |
8ae28ff to
2935f72Comparejuanarbol
commented
Jul 21, 2020
Closing due inactivity |
May fix: #28635
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes