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

So I understand correctly, do you mean if there's both an IntersectionObserver type of code _and_ this new event handling? I can't immediately think of a situations where this can cause a problem where both handlers are triggered in a loop. The only way that would be possible is if one of the handlers changes layout of the page such that the affected c-v element keeps being toggled between skipped and not skipped states. But that seems like a behavior that could already be caused with only one of IntersectionObserver or this new event. IOW (and IMHO), nothing fundamentally changes now that there are two different ways to observe these state changes.

I hope that answers your question

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

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