@hober and I looked at this in a breakout and sympathize with the concerns raised in issues [dtapuska/documentaccess#2](https://github.com/dtapuska/documentaccess/issues/2), [dtapuska/documentaccess#4](https://github.com/dtapuska/documentaccess/issues/4), and [dtapuska/documentaccess#6](https://github.com/dtapuska/documentaccess/issues/6). Developers are going to think that this is a security/privacy feature and not understand that it is mostly about performance benefits due to underlying architecture (running in same thread or not, etc) that they might not even understand. It is also quite concerning that this adds yet another set of knobs for how to configure the whole feature/document policies and this doesn't seem to be a simplification, which @zbarsky pointed out in this comment: https://github.com/dtapuska/documentaccess/issues/2#issuecomment-517789237 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/397#issuecomment-634075283
Received on Tuesday, 26 May 2020 14:52:57 UTC