Hello shmulik hakipod, as you said, depending on which part of the button you click on, your trigger fires or not. That happens because sometimes you click the <button> element, but in other cases you clicked the <div> element that is inside it; so you need to consider these last cases. To do that, you could change the condition when you fire the trigger to start considering also the elements inside the button. There are different solutions you could implement, for example, you could use a condition like the following one:
Click Element, matches the CSS selector, button[id="click-button"], button[id="click-button"]*
With this condition, you won’t only consider when the users click the button, but also when they click what is inside it. I hope this will help you, if not make me know
A helpful solution!
Does that mean I can use , to separate different CSS selector within one trigger ?
I used to defining two triggers for parent elements and child elements individually to make the tag work.
Exactly, you can use the comma to consider multiple CSS selector at once in the same trigger or variable. If the triggers are used in the same scenario for fire the same tag, yes, i would recommend you to use multiple CSS selectors separated by a comma instead of having one trigger for each CSS selector.