Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616)

Yeah, in a way, you’re hitting the fundamental limitation of custom element lifecycle callback timing. Unless callbacks are fully synchronous, it’s always possible for a callback to called with an outdated value, or some elements to be in an out-dated state.

In general, mutating another element inside a custom element callback should be considered an anti-pattern and should be avoided because of this problem. Making such a mutation can lead to very fragile racy components that steps on each other’s toes as many apps that use mutation events have demonstrated in the past 10+ years.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/616#issuecomment-266617530