SOLVED: Opacity value added to interaction trigger

Bricks Version: 1.6.2
Browser: Chrome 109.0.5414.87
OS: macOS Ventura

  1. Enable custom breakpoints and set to mobile-first
  2. Create an element (button) that will trigger an interaction (ex., open a popup)
  3. Set an action and set the animation type to fadeIn
  4. Notice how the button on the frontend has disappeared due to the opacity value coming from the animate.min.css (the animation styles).

This can be resolved by adding an opacity value to the element, but this wasn’t needed before. Also, I’m concerned about what other styles will be applied to the trigger element with other animation types (not just the opacity). I’m guessing there’s a CSS specificity issue happening somewhere.

Let me know if you need any more information!

Hi Ben,

Thanks for reporting the issue.
Yes, I can replicate this bug and added it to the bug tracker.


1 Like

Since the subject of this ticket states it’s a “mobile first” issue I just wanted to add that it’s not just mobile first but the same problem with regular breakpoints.

With the following interaction configuration (see screenshot) attached to a button the button gets hidden.


I’ve updated the subject to make sure it’s tracked correctly :wink:

Yes, noticed on that :slight_smile:

yeah, have exactly the same issue - can’t trigger animation on popup as trigger button disappears. Hope it’s gonna be fixed with the next release

Hi guys,
We’ve fixed this bug in Bricks 1.7 beta, now available as a manual download in your Bricks account: Account – Bricks

Please let us know if you are still experiencing issues.

Best regards,

1 Like