You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you have a block with falsy conditional block that has a child block with motion effect(s), the motion effect frontend script will not be loaded for that page. This causes error to subsequent blocks that use motion effect.
Note that this only happens when the said block is the first block in the page that uses motion effect.
To Reproduce
Steps to reproduce the behavior:
Add a Columns block
Add a Heading inside the Columns.
Set the Conditional Display of the Columns block to a falsy one (e.g. Login Status > Logged-Out Users while viewing the page as logged-in user).
Set the Motion Effects of the Heading block (e.g. Entrance Animation)
Add another Heading below and set its Motion Effects.
See that the Column is not displayed as expected, but the Heading below is also not shown due to the faulty entrance animation (stuck at stk-entrance with 0 opacity)
Expected behavior
Falsy conditional display is expected to not load the block's frontend script as if the block is not present at all. However it should not prevent subsequent loading.
Describe the bug
When you have a block with falsy conditional block that has a child block with motion effect(s), the motion effect frontend script will not be loaded for that page. This causes error to subsequent blocks that use motion effect.
Note that this only happens when the said block is the first block in the page that uses motion effect.
To Reproduce
Steps to reproduce the behavior:
stk-entrancewith 0 opacity)Expected behavior
Falsy conditional display is expected to not load the block's frontend script as if the block is not present at all. However it should not prevent subsequent loading.
Reported Issue: https://www.notion.so/Motion-effects-issue-with-Metabox-2ed584f29f4c80b8b94dfacf15d950e3?source=copy_link
Related to #3688.
Screen.Recording.2026-03-24.at.11.40.01.PM.mov
Also happens on anything with a frontend script: