After hours of searching, it turns out that ticking “include component location into bounds” seems to resolve this issue as explained in this post
After hours of searching, it turns out that ticking “include component location into bounds” seems to resolve this issue as explained in this post