- From: Darien Maillet Valentine <notifications@github.com>
- Date: Wed, 23 Nov 2022 13:37:21 -0800
- To: whatwg/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 23 November 2022 21:37:34 UTC
> This is coming up now because in blink we're [trying](https://groups.google.com/a/chromium.org/g/blink-dev/c/j7vOAkMbu_M/m/OmlnogDoAgAJ?utm_medium=email&utm_source=footer) to expose the [Report interface](https://w3c.github.io/reporting/#idl-index) and needing to do a bunch of web compat analysis to figure out whether or not we can do so safely. What is the cost/benefit tradeoff of exposing interfaces like this one? Report is already exposed in gecko, which was a relief because at one point there was a bug with its toJSON that we needed to patch. It was lucky that we didn’t have this issue in Blink, where it wouldn’t have been similarly addressable. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/webidl/issues/1236#issuecomment-1325687400 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/webidl/issues/1236/1325687400@github.com>
Received on Wednesday, 23 November 2022 21:37:34 UTC