For the possibility of displaying mainArea content over the complete width of a page a bodyClass 'col' was implemented into the BodyClassResolver.java.
'col' would mean, that the V-Navigation&extrasArea&promosAre are disabled.

Now there are two problems about this col:
1. 'col' bodyClass is not defined yet in the css. When a page gets rendered with col, the mainArea width is very small (like on nav-col-subcol).
2. When V-Navigation is active, but does not show yet because the depth of the page is to high, the bodyClass resolved is 'col' in stead of 'nav-col'.
Only when the V_Navigation is really deactivated it should render 'col'.
For example: Configuring the H-Navigation with two levels. Adding page HomePage-SectionPage-SiteMap
The SiteMap page is displayed on H-Navigation level 2 -> no V-Navigation is rendered. But the bodyClass should remain 'nav-col' for having the space of navigation at the left side. Before implementing the 'col', this was at least the standard behavior of all pages -> leaving at the left side the space for navigation as long the navigation is not generally (or on specific template) deactivated.

I thing the concept of 'col' and 'nav-col' (and eg 'col-subcol' to 'nav-col-subcol' should be looked at and be clearly defined and implemented into css.