Tristan Fraipont

If I may, I believe the WHATWG's TextDecoder option would be your best move here. As already said it is future-proof, and [can be polyfilled](https://github.com/inexorabletash/text-encoding) if needed. It would also...

Fair enough, I opened https://bugzil.la/1784187 however I still believe this "Ensure observer runs" is quite obscure as to "how" it's supposed to do this, and "when" it does this. Maybe...

https://github.com/whatwg/dom/issues/1038#issuecomment-985733476 > that returns a `Promise` that is resolved with `undefined` when the next event type is dispatched. Really? I can't find the rationale for this in this thread, is...

Great that even avoid the ugly line break ;-)

Regarding the mutability of `CanvasGradient` objects, I want to clarify that modifying it through `addColorStop()` is currently the only way to define a non transparent `CanvasGradient` object. I don't think...

I'm not sure what would be the real benefit of this... We can already apply all these filters through `url(#svg-filter)`. This *should* theoretically not even require access to the DOM...

> it's not clear at this point that any web engine can build a SVG on a WebWorker It seems indeed none can do it yet, but OffscreenCanvas support is...

> It lacks a clear definition for the primitive inputs and result. It does not specify a name for the result. It has only 'SourceGraphic' and 'previous' as builtin names...

Could you clarify what in this API makes the users expect "grouped effects" more than the simple CSS filters syntax we have for years? It seems that you want a...

Reading back the [first comment by @litherum](https://github.com/whatwg/html/issues/5621#issuecomment-641110019) it seems the Webkit team is arguing against `ctx.filter` as a whole. [This already shipped in 2016](https://github.com/whatwg/html/pull/978), Webkit indeed still doesn't support it...