At the moment, turning off 'fixed header' in a CMS Record causes unintended behaviour. The header is loaded inside the #main-content div, and is therefore clobbered by the __loadPageContent() function when a new page is accessed in the site navigation.
A related problem occurs with custom headers. The header background is hard-coded into the php file that generates the site, and is difficult to change. In addition, the user is only offered 32px of height to contain their custom header.
At the moment, turning off 'fixed header' in a CMS Record causes unintended behaviour. The header is loaded inside the #main-content div, and is therefore clobbered by the __loadPageContent() function when a new page is accessed in the site navigation.
A related problem occurs with custom headers. The header background is hard-coded into the php file that generates the site, and is difficult to change. In addition, the user is only offered 32px of height to contain their custom header.