@mdtauhid001 Thanks for reporting this! I checked with the team and we’ve already got a bug fix in progress. Should be resolved in the next Atomic Blocks update.
One extra note, Atomic Blocks is no longer where we are dedicating time to active development of our block library. Instead, active development is now happening in our replacement plugin, Genesis Blocks.
https://wordpress.org/plugins/genesis-blocks
While we will be fixing bugs like this one in Atomic Blocks for a time (so people have time to switch to Genesis Blocks), eventually this plugin will be retired and no longer maintained.
We highly recommend switching to Genesis Blocks and running the migration tool, especially if you need this bug resolved quickly, since the latest version of Genesis Blocks doesn’t have this bug.
