That’s assuming the extension manages to hit your trigger correctly. They did not make the js call, just blocked the div. Oddly, they left our full page control block in place. We had to modify our triggers to make it work.
We had a form button on a div slide in with a 30% dimmed background div behind it. The button just did a JS call to trigger to safe cookies or not and unblock the back div.
The browsers were just unblocking the banner div on us they weren’t making the button call. I’m sure they do something very smart to try to figure out how to automatically click okay or cancel, somehow it just didn’t line up with what we had written.
That’s assuming the extension manages to hit your trigger correctly. They did not make the js call, just blocked the div. Oddly, they left our full page control block in place. We had to modify our triggers to make it work.
Is the trigger a js event, or an api call, or what?
We had a form button on a div slide in with a 30% dimmed background div behind it. The button just did a JS call to trigger to safe cookies or not and unblock the back div.
The browsers were just unblocking the banner div on us they weren’t making the button call. I’m sure they do something very smart to try to figure out how to automatically click okay or cancel, somehow it just didn’t line up with what we had written.