Re: [w3ctag/design-reviews] ContentVisibilityAutoStateChanged event (Issue #756)

@ylafon and I took a look at this during our London F2F this week and, broadly speaking, this seems reasonable to us. We're wondering if you've thought about this edge case, though:

Say you have a large website that many developers have hacked on. Before the introduction of this feature, someone does something roughly equivalent with `IntersectionObserver` and `MutationObserver` as you've alluded to. Later, after the introduction of this feature, someone does something else on the same site, with the same subtree, with the new element. Is there any risk that this new event handler could cause a cycle with the old code? Is there a way for the spec or the implementation to mitigate this?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/756#issuecomment-1195600551
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/756/1195600551@github.com>