Javascript API click functionality

Sure -- thanks for the help!

Here's the script that is inserted into the page header using the Insert Headers and Footers plugin. It is a lightly modified version of the code suggested at the very bottom of the Buttonizer Javascript API page.

<script>
window.addEventListener("buttonizer_initialized", () => {
document.querySelector("#open_click").addEventListener("click", () => {
window.Buttonizer.open("32b45974-988a-45c8-9392-da32ff0773b0");
});
document.querySelector("#open_mouseover").addEventListener("mouseover", () => {
window.Buttonizer.open("32b45974-988a-45c8-9392-da32ff0773b0");
});
document.querySelector("#open_mousedown").addEventListener("mousedown", () => {
window.Buttonizer.open("32b45974-988a-45c8-9392-da32ff0773b0");
});
});
</script>

And here's an example of the button that isn't working:
<button id="open_click">Click</button>

But change the id to "open_mouseover" or "open_mousedown" and it works fine.

You can see it all in action here: Buttonizer Test Code

OK -- new issue.

Everything worked perfectly until I followed the new Buttonizer prompt to migrate to the standalone version. Now none of the javascript buttons are working at all.

Any ideas for that one?

UPDATE: I think I found the problem. It works fine when controlling all groups but it's not finding the group IDs when I include them in the (). And when I run this code...

window.Buttonizer.groups().forEach((obj, key) => {
console.log(Button ${obj.id} is ${obj.isOpened() ? 'opened' : 'closed'}!);
});

...it now shows new group IDs every time I load the page! So it appears that either the standalone version needs to offer static group IDs, or I need a new way to recognize groups on my side.

UPDATE2: It's not clear what happened (the only thing I did was disconnect/reconnect to Buttonizer) but now everything is functioning correctly again. If that was one of you guys, nice work!

Jasper I can ensure that the standalone IDs are static saved in the database and don't change or rotate, so it could be that the IDs were mixing up/switching between with the cached WP Buttonizer data and the standalone (which actually would be weird as the IDs should have stayed the same on migrating).

The IDs were definitely changing for a while there. I ran the "loop through group IDs" script multiple times on one page and it showed the same IDs. But as soon as I refreshed the page the IDs were randomized again. It was clearly why the open function wasn't working, as the console would give me an error that is could no longer find the ID the script was referencing. But for whatever reason it's fixed now and the original IDs still work fine.

Jasper Can you elaborate on this issue a little bit more? Does it behave different as soon you disable that setting in your code or in our code?

When you have "close on button click" turned on, the mousedown function acts like a momentary switch that opens the Buttonizer group only while you hold the mouse button down (it closes the moment you release the button). But with "close on button click" turned off, mousedown acts just like click (it only closes when you click on it a second time). Again, maybe that's actually normal. But it's an interesting difference.