Re: [heycam/webidl] Added a definition of {{StringContext}} extended attribute. (#841)

> where the check may be applied effectively via extended attribute.  alternatively, multiple places in DOM and HTML would have to be modified separately

This was not the case for [CEReactions], right?  Why is this case fundamentally different?

> in short, it's advisable to run TT operations before DOM gets to mutate the tree.

As I said above, that does not require doing it as part of IDL argument conversions.

> running them after the data was already processed (e.g. inserted into the DOM) in a separate microtask like CEReactions

I didn't say to use the same semantics as CEReactions, which is obviously a daft thing to suggest, so I'm not sure why we're discussing that strawman. I asked why we can't have the semantics of "run before any of the operation steps".  Sort of like how all CanvasRenderingContext2D methods have a first step of "validate all the doubles".  Those are written out by hand in the spec right now, but they could be done via extended attribute (and are implemented that way in Gecko, fwiw).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/pull/841#issuecomment-586130844