Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995)

Hi @camillelamy, thanks for bringing this to us.  We're still struggling a little bit with the explainer here, but there are a few things you might add to help us a little.

1. What is the user need that this addresses?  There is some mention of performance benefits in your writeup here (~40%! \[citation-needed]), but that isn't really substantiated.  Can you give us some examples of real-world scenarios in which this would be used and provide material end-user benefit.  In particular, why do these applications need to jointly use popups and this sort of arrangement? In "use cases" you list "App with cross-origin popup" and state "The user would like some of their compute heavy web apps to be faster" - but there is no discussion of why these applications must exist cross-origin.

2. What are the trade-offs taken for this?  Or, what are the risks that we'd be taking on by allowing this loosening of cross-origin isolation?  The explainer focuses exclusively on arguing *for* the proposal, but if we're going to make a reasoned decision, we need to understand the cost of the change.   Are there any safeguards that might be needed to mitigate these risks?

3. Are there cases where applications might want to use `SharedArrayBuffer`, but are unable to employ a fallback method, such that enabling easier access to the capability would dramatically simplify the deployment/development of those applications?


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/995#issuecomment-2415956163
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/995/2415956163@github.com>