The element is contained within a group which behaves as responsive (row). The width of the group is not analogous to the width of the page, i.e. As the page gets smaller, there are points where the group may become larger, then start becoming smaller again.
One more reason is that atleast the way I’m working, I design each part of the app as a reusable element. So that means that the same element can be used in a page as a 320px width element while in others as 600px or more and this is irrelevant to the width of the page at that moment. This gives me tremendous flexibility for designing my pages but in order to make full use of this method, I need a better way of handling element visibility.
In order to truly capture the size of the element, we need this to be tied to the actual size of the element, not it’s group.
This for sure… I’ve been having the exact same issues.
I hope they add a conditional for ‘Container Width’ as well as the current one for ‘Page Width’ once the new engine is out of Beta (which would be the true equivalent of the hiding rules on the old engine).