Fix 'trusted-click-element' — element was removed and added again before it was clicked

[Alex-302]

For example - with iubenda.com consent management platform:
https://tecnologia.libero.it/fotone-altissima-energia-piu-potente-registrato-arrivato-terra-mette-crisi-scienziati-80320
https://coolsoft.altervista.org/en/virtualmidisynth

coolsoft.altervista.org#%#//scriptlet('trusted-click-element', '.iubenda-cs-customize-btn') works an opens options. But the scriptlet cannot click the Reject All button. It works with #iubFooterBtn.

[Sergey-Lyapin]

The scriptlet also doesn't work at virginaustralia.com, for example these scritplets don't work:

virginaustralia.com#%#//scriptlet('trusted-click-element', '#cookieAcceptanceBtn', '', '1000')
virginaustralia.com#%#//scriptlet('trusted-click-element', '#cookieAcceptanceBtn')

[AdamWr]

Regarding coolsoft.altervista.org, maybe it's already fixed?
The rule like this:

coolsoft.altervista.org#%#//scriptlet('trusted-click-element', '.iubenda-cs-customize-btn, .purposes-content .iub-consent-buttons .iub-btn-reject, #iubenda-iframe-popup button#iubFooterBtn')

works fine on my end.
By the way, after clicking on the Reject all button, it's necessary to click on the Save and continue otherwise modal will be not closed.

---

Regarding virginaustralia.com, it looks like the problem is that when element is clicked "too fast", then event listener is not registered yet.
Another problem (when delay is used) is that website removes this button and add it again, but it seems that scriptlet keeps reference to removed button and tries to click it, but element it's not in the DOM.
As a temporary workaround rule like this:

virginaustralia.com#%#//scriptlet('trusted-click-element', '#cookieAcceptanceBtn[class*="__button--"]')

can be used.