Meteor’s conditional helpers add/remove DOM elements, which diverges from the more ‘conventional’ behavior you’d expect where all elements are present in DOM and being mutated by css classes etc.
the easiest way to achieve this conventional behavior, at least in this use case, would be to move the conditional block into the tag’s class attribute:
It’d be nice if Blaze was smarter and would detect the difference (similar to React) and it would therefore realize that it’s the same div but with or without a class.