Hopefully I am missing that there is a simpler way to create a footer that spans the entire browser window, always pushed to the bottom of the page by the content above it, without having to create a full box model layout.
While I love FW and its master page metaphor, box models are a PITA and break too many features. Having to resort to one for such a common web design element is a real drag.
On 5 Oct 2010, at 14:18, Solutions Etcetera wrote:
Hopefully I am missing that there is a simpler way to create a footer that spans the entire browser window, always pushed to the bottom of the page by the content above it, without having to create a full box model layout.
While I love FW and its master page metaphor, box models are a PITA and break too many features. Having to resort to one for such a common web design element is a real drag.
But I am afraid I am not having a good day. Your solution seemed a very good one, and after quite a few hours of re-laying out my site to this model I have once again hit a wall.
I created a master page with the three inline divs for header, body and footer, along with inline divs inside those for content.
I then created a floating div for my css menu bar which sits atop everything near the top of the page. The whole purpose of this is to allow me to make changes to my menubar and keeping the master settings across all of the pages.
This looked like it was going to work until I created all of the pages to link to the menubar, only to find that the sub-menus are drawing in back of the content in the inline “body” div.
Freeway shows my menu at the bottom of the item list so I am assuming it is on top but that doesn’t seem to be the case. I have selected the menu on the master and selected bring to front but the results are still the same.
After looking at the code, I see that a z-index of 1 is being assigned to the menu div… I guess because FW is oblivious to any other divs used in the inline model.
Setting the z-index attribute of the menu div manually to 99 seems to have made things happy.
On 5 Oct 2010, at 21:48, Solutions Etcetera wrote:
After looking at the code, I see that a z-index of 1 is being assigned to the menu div… I guess because FW is oblivious to any other divs used in the inline model.
Setting the z-index attribute of the menu div manually to 99 seems to have made things happy.
Well… that was my point. Freeway’s code does not seem to be cognizant of the other divs in this kind of layout model - so even after bringing it to front, FW continued to write code with a 1 based index.
My guess is that divs that are inline are all indexed 1… and any floating divs on top also start out at 1.
Inflow divs have no z-index, which is equal to a z-index of 0.
On 5 Oct 2010, at 22:34, Solutions Etcetera wrote:
Well… that was my point. Freeway’s code does not seem to be cognizant of the other divs in this kind of layout model - so even after bringing it to front, FW continued to write code with a 1 based index.
My guess is that divs that are inline are all indexed 1… and any floating divs on top also start out at 1.
Perhaps I am not making myself all that clear. In your model above, you have the basic box model with in flow divs, and then recommend placing layered elements within them, using the relative page layout action to manage their size and position. The first one of these in each inflow div is going to have an index of 1, the second of 2, etc.
Placing a floating div on the page above any of these (not inside any other element) is also going to start with an index of 1… so you may see unexpected results with layers unless you manually apply an index for the floating layers.
Child elements start at Z:1, but that’s 1 relative to their nearest parent. Of that parent is at z:29, then that’s going to be higher than another element which is a child of the page and is at z:20.
There is one html element in the inline body element (inside, but not inline with blue area). The menu element is a layer on top of the entire page. As FW outputs the code, both have a z-index of 1. The menu is clearly behind the element in the body.
I can’t see your example pages at the moment (all I get is a 404 page)
but you may find a solution in this thread from earlier this year; http://freewaytalk.net/thread/view/64657#m_64657
Regards,
Tim.
On 6 Oct 2010, at 01:54, Solutions Etcetera wrote:
There is one html element in the inline body element (inside, but
not inline with blue area). The menu element is a layer on top of
the entire page. As FW outputs the code, both have a z-index of 1.
The menu is clearly behind the element in the body.