In the docs it says it uses a mutation observer under the hood and disconnects when the element loads. API Reference | CC Developer Portal
I notice some elements re-render repeatedly shaking loose event handlers and updates previously made. Does observeElement take this into account? Also is there any way to do this for multiple elements like a querySelectorAll version of this?
Thanks!
Hello
Thanks for raising this! I took it to our devs, here's what came back.
observeElement is one-shot. It disconnects the moment the element first shows up, so it won't fire again when that element re-renders. onEvent behaves the same way since it's built on observeElement. And there's no querySelectorAll version today, so it's one selector per call.
On the re-rendering itself, the honest answer from our devs is that it depends on the element. Some of our markup is static and stays put, other parts are rendered and managed by our JS framework, and there you're working against its render cycle, so handlers and changes can get dropped on the next tick. Internal class names can shift between releases too.
Which elements are you seeing this on, and are you working from a custom widget or from third-party scripts / header-footer?
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
