- From: Tab Atkins Jr. <notifications@github.com>
- Date: Fri, 29 Apr 2022 12:08:57 -0700
- To: whatwg/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 29 April 2022 19:09:09 UTC
If it actually cost impl effort I can potentially agree, but I don't see how that's the case. (The *restriction* doesn't cost impl effort either, except in their internal binding generator that parses IDL, but it costs spec effort to remember these odd inconsistencies, and results in oddly-designed APIs when someone blindly designs around the restriction rather than revisiting the original question.) And looking into this more, it actually seems like the OP accidentally discovered a *different* error actually - the [attribute getter algo](https://webidl.spec.whatwg.org/#dfn-attribute-getter) runs some steps if called specifically on an interface and with a regular attribute, but those steps should apply to namespaces as well, which can also have (readonly) regular attributes. As currently written, it looks like namespace getters would bypass the security check, for example. Fixing *that* would have resolved the OP's contradiction as well. Am I reading this wrong? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/webidl/issues/1000#issuecomment-1113637796 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/webidl/issues/1000/1113637796@github.com>
Received on Friday, 29 April 2022 19:09:09 UTC