If you are creating a positioned layout (the usual defaults in Freeway) then each HTML element you draw on the page (or otherwise get on the page, as in from a master page or similar) stands alone. It’s like an animation cel, sitting on its sheet of glass in the multi-plane camera. When you move it, it doesn’t touch anything else, it just slides independent of everything else. So if you have more content on one page than another, or if your visitors use their browser settings to enlarge the text for easier reading, the elements that grow and shift do not impact one another, leading to overlaps and crazy cubist layout interpretations.
When you say you want a footer to be at the bottom of your content, you need to take that into consideration. Sure, it may be at the bottom now, but when my friend Beverly comes around with her browser set to compensate for her awful macular degeneration, she will see your footer somewhere around the second paragraph of text content.
The correct solution to this problem is a fully inline layout, where the content above the footer is able to push the footer down in response to Beverly’s browser or variable content. This requires you to abandon your normal work pattern in Freeway, and embrace a different style of working, with HTML items inserted into parent HTML items as if they were individual characters of text. You use floats and padding and margins to create the spacing of your individual page elements, and once you’re done, the page is able to withstand text zooming and other horrors, and the footer will be pushed down precisely as much as necessary (and no further).
There is an Action in Freeway 5.5 and up called Relative Positioned Layout, or RPL for short. This attempts to reverse-engineer your positioned layout into an inline layout, giving you the benefits without the (sometimes mind-bending) work required to set one up. I recommend you try that first.
But there is one more thing to think about with Master Pages. In Freeway 6, they have a new granularity that makes it possible to have a master element on the child page in a position other than the one specified on the Master Page. Try this and see if it works for you (note that it will not, and cannot fix the issue of content appearing at different heights in different browsers – that’s what an inline layout is for).
- Make your master page crazy-tall. Put your footer at the bottom of it.
- On each child page, select the footer element and (holding down the Shift key to constrain the move) drag the footer north until it is where you expect it to be.
- Notice in the Inspector that the “Use Master Content” checkbox will remain checked, while the “Use Master Settings” checkbox will un-check to note this separation from the master.
If you subsequently make changes to the footer on the master page, you will (or should, it’s a bug if not) see the content update on every page, while the position remains detached from the master’s original.
Walter
On Feb 21, 2013, at 5:52 AM, Daemon wrote:
Hi,
I need the same footer on every page so I created one in master page. How can I do this in a way that it stays at the end of each page?
How do I create a footer?
Should the Master Page height be the same as the one of regular pages? Does this matter in some way?
Where should I place the footer in my master page? Does it need special proprieties?
I can create useful footers if I place one in a page and copy paste to the others, but I wanted to avoid this and learn the correct way (if there’s one).
Thanks.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options