Re: [heycam/webidl] Define the `[CrossOriginIsolated]` extended attribute. (#883)

> Sounds like it needs two rules, one to prevent descendants to use `[CrossOriginIsolated]` when there is `[SecureContext]` and vise versa.

I think we'd have one rule for `[CrossOriginIsolated]` and another for `[SecureContext]` along the lines of what @annevk suggested.

> I wonder we could rename `[SecureContext]` to `[Context=Secure]` and `[CrossOriginIsolated]` to `[Context=CrossOriginIsolated]` so that we can have only one check: whether descendants have `[Context]` or not.

This is more or less the spelling of the proposal in https://github.com/mikewest/securer-contexts#a-proposal (`[SecureContext=(Transport,Isolation,Injection)]`). That's a fine approach if it's what we end up wanting. I think I'd prefer distinct attributes, however, as that would allow us to invert the `[SecureContext]` model entirely (https://github.com/heycam/webidl/issues/876).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/pull/883#issuecomment-627962009