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

Make high resolution time dependant on cross-origin isolated #89

Closed
annevk opened this issue Apr 8, 2020 · 7 comments · Fixed by #93
Closed

Make high resolution time dependant on cross-origin isolated #89

annevk opened this issue Apr 8, 2020 · 7 comments · Fixed by #93
Assignees
Labels
enhancement hackathon_15_09_20 hackathon_2020 security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.

Comments

@annevk
Copy link
Member

annevk commented Apr 8, 2020

With #88 solved, it would be good if the 5 microseconds resolution would be made conditional upon cross-origin isolated.

See whatwg/html#4734. Though see whatwg/html#5435 about potentially having to refer a slightly different concept.

@yoavweiss
Copy link
Contributor

/cc @mikewest

@mikewest
Copy link
Member

mikewest commented Apr 8, 2020

This sounds pretty reasonable to me.

@yoavweiss
Copy link
Contributor

Should this be blocked on the definition of isolated contexts?

@npm1
Copy link
Contributor

npm1 commented Apr 8, 2020

Chrome's current resolution is 5 microseconds for platforms other than Android. Does that mean we'll need to coarsen the timer more for these platforms? What would be the new maximum resolution for non-isolated?

@plehegar plehegar added enhancement security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. labels Apr 23, 2020
@bdekoz bdekoz pinned this issue Apr 23, 2020
@yoavweiss
Copy link
Contributor

This was discussed at a WebPerfWG call a couple of months back.

It was decided that once the underlying primitives are integrated into HTML (which I believe they now are), we'd estimate if this goes into L2 or L3 based on the changes themselves.

@npm1
Copy link
Contributor

npm1 commented Aug 21, 2020

Is cross-origin isolated now shipped in browsers? What's the next step here?

@yoavweiss
Copy link
Contributor

I think the next step is for me to try and take a stab as defining something that outlines what browsers are currently doing, and what COEP/COOP would enable them to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement hackathon_15_09_20 hackathon_2020 security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants