-
Notifications
You must be signed in to change notification settings - Fork 67
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
Web Integration: Performance mixin? #387
Comments
cc @ptomato |
@caridy @leobalter Whoops, this looks like my mistake. Performance is still marked as |
To be clear, based on the rationale in #393, performance shouldn't be included (and in general, I'd support its exclusion). |
I don't think performance violate the criteria that we are using for inclusion/exclusion. Does it break confidentiality? Is Update: after further review of the new API (https://developer.mozilla.org/en-US/docs/Web/API/Performance/measureUserAgentSpecificMemory), that seems a lot more problematic. Certainly leaking origin information. |
Also just generally “host access” |
I have added my notes on |
@ptomato is there anything else pending to exclude |
Yes, we should remove the |
I found that these were already reverted.
(So that's why they didn't show up in WPT's IDL files! ref #387 (comment)) So I think we're good in terms of excluding |
In #331 a few performance related PRs were merged; but I don't think any of them merged an actual performance object. In the hr-time spec that's the
If we want to expose the Performance interfaces, we need a Performance object to act as receiver for some of the methods of interest.
The text was updated successfully, but these errors were encountered: