Re: [webkit-dev] Request for position on the Origin-Isolation header
Hi, On Thu, Aug 20, 2020 at 8:51 AM Domenic Denicola wrote: > > Hello webkit-dev, > > I've been working on a new header called Origin-Isolation, which is a way of > allowing origins to opt-out of using document.domain and cross-origin > sharing of WebAssembly.Module, and thus allowing the browser to put them into > an origin-keyed agent cluster instead of a site-keyed one. This could in turn > allow the browser to make better behind-the-scenes decisions for process > isolation, or other resource allocation decisions, since sites no longer have > any ways to synchronously communicate cross-origin. > We haven't had a chance to fully review the proposal but we didn't find anything we'd immediately object to. It seems like a reasonable idea. I feel like I saw some discussions of also differentiating based on protocol (treating http://webkit.org and https://webkit.org differently). Do you know you've already had such a discussion and if so what the outcome of that discussion was? - R. Niwa ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Request for position on the Origin-Isolation header
Hello webkit-dev, I've been working on a new header called Origin-Isolation, which is a way of allowing origins to opt-out of using document.domain and cross-origin sharing of WebAssembly.Module, and thus allowing the browser to put them into an origin-keyed agent cluster instead of a site-keyed one. This could in turn allow the browser to make better behind-the-scenes decisions for process isolation, or other resource allocation decisions, since sites no longer have any ways to synchronously communicate cross-origin. Relevant links: * Explainer: https://github.com/WICG/origin-isolation * HTML spec PR: https://github.com/whatwg/html/pull/5545 * Test suite: https://github.com/web-platform-tests/wpt/tree/master/origin-isolation * Gecko "worth prototyping" standards position: https://mozilla.github.io/standards-positions/#domenic-origin-isolation A natural question one might ask is how this relates to COOP+COEP? The explainer has that covered: https://github.com/WICG/origin-isolation#coop--coep Thanks for your time! -Domenic ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Suggesting to enable paint timing by default
On Thu, 20 Aug 2020 at 6:26 Maciej Stachowiak wrote: > > > On Jul 17, 2020, at 12:12 AM, Noam Rosenthal wrote: > > > > On Thu, Jul 16, 2020 at 11:03 PM Keith Miller > wrote: > >> Results appear to be neutral on the page load time benchmark, so you >> should be good on that front. I don’t know who the best person to vet the >> maturity of the code is though, sorry. >> > > Thanks a lot Keith, I appreciate it! > @Maciej Stachowiak , what would be a good way to assert > whether the code maturity is good enough to enable paint timing by default? > The original code was reviewed by smfr and initially by zalan. It's > covered by over 30 tests, mostly WPT, and A/B tests show no effect on load > times as per Keith's check. > Would asking for additional reviews be the next step? From whom? > > > At this point, if a reviewer approves a patch to enable it by default on > trunk, I think you are good to go. > > As a courtesy to Apple, I’d ask you to hold off on landing until > mid-September, but that is optional. > Great The patch has already been reviewed, I will re-land it in mid September. Thank you! > > - Maciej > ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
