My point is, nothing is impossible and our imagination can take us only to how far we want to go. That is exactly why ABM is beyond normal, its extra ordinary.
That is why also in the feedback app we have a feature request for anything doable (that does not break existing code) and will work and other important considerations like ABs time.
Looking at just the additional features that ABM already has is evident to it breaking grounds and going to infinity and beyond. Did I just quote toy story?
If everything in ABM is a component and has a reference I.e and id, and using css to turn off or on the visibility property with existing abm visibility enumeration could work and is doable and wont break any existing code, then part of my question is already solved.
I dont think ABM was ever in the first place bound and limited to conventions, otherwise we would only be having components as equal with the same look as to what material designs has in store, it has gone beyond the call of duty to be the excellent tool it is, outside that box frame, with additional components and exciting features driven by the same imagination of AB and people who request features. I understand that those are scaled, importance and value add, besides no one can please everyone otherwise we would have dysfunction. Thanks for the chat.