Caridy Patiño
Caridy Patiño
Yes, we are intentionally keeping this simple, `ShadowRealm.evaluate`, and `eval` inside the shadow realm are sharing the same evaluation path, which hits the host hook, which relies on the settings...
It seems that we need more clarifications here. From what I remember (@mhofman keep me honest here), TT is not going to be available inside a ShadowRealm initially. Instead, we...
> Calls to `eval()` and `new Function` inside the ShadowRealm must _not_ go through the TT checks of the outer realm, but I also don't see a reason to not...
@lukewarlow thanks for reopening this. we certainly need this resolved to be able to move forward with the regulations in Europe. cc @gregwhitworth
@annevk I think the main incentive here is to prevent evaluation in browsers without TT, as this constitutes a security problem today with no way to mitigate it without introducing...
Same here, I'm interested!
I'm very supportive of this additional restriction for `eval` and `Function`. cc @nicolo-ribaudo
This matches my mental model as well. Just like `shadowroot` attribute triggers the creation of a shadowRoot instance, the `scope-custom-elements` does the same, it creates a brand new (therefore, an...
@rniwa can you provide some input here? It seems doable, and will facilite few things, but we have limited knowledge here.
Ok, lets move back there then! @leobalter is taking care of it I believe.