At the bottom of our homepage found here sy.pe you will see a space (about a 5mm margin) showing the background image. This displays as expected on all the pages with the exception of these two pages found here: sy.pe and sy.pe
Both of these pages contain similar content. What is the reason I’m not getting the margin I require at the bottom of the page like the rest of the site?
a quick examination of your style code shows the pages that have “space” at
the bottom between the window edge and the “page” edge have one of the divs
at the bottom to be taller than the item it contain - so tall as to stretch
beyond the bottom of the “page”-looking thing exactly the amount you see in
the window. This is what makes the window believe there is something down
there to scroll to. On the pages without that bottom space, there isn’t
anything to reserve that space.
I’m betting that if you place an empty box below the “page-looking” thingy,
that is exactly the height you want this “space” to be, that it will make
the window (and your viewers) believe there is something there to scroll to
that being invisible will still look like space.
–
Ernie Simpson
On Mon, Jun 24, 2013 at 5:17 AM, Tony email@hidden wrote:
Hi All
At the bottom of our homepage found here sy.pe you will see
a space (about a 5mm margin) showing the background image. This displays as
expected on all the pages with the exception of these two pages found here: sy.pe and sy.pe
Both of these pages contain similar content. What is the reason I’m not
getting the margin I require at the bottom of the page like the rest of the
site?
Believe it or not, I’m a print designer as well - just with more time on
the ground in Webdesignistan… so, let me translate the lingo for you.
A div is an element in HTML that acts like a “box” or container - it can be
visible (color, border, background-image) or invisible (but still with
dimension, padding, margins). If you work with inDesign, the concept will
seem similar. If you look at your page code, you will “see” the tags that
identify where those divs are (
).
In Freeway Pro, what will become HTML divs are better known as “layered
html items” and look and act like the content-boxes from inDesign. Every
layered html item in FWP has a unique “name” and this name is attached to
the div in the page code as an id ( eye-dee ) tag. If you look again at
your page code, you will see what I mean (
). Of
course, page code is a lot more complex than that, but that is the best way
to begin to “see” the results of what you are making in FWP. Do it long
enough, and you will see beyond the “gibberish”.
So, all I’m really saying is – on the pages where you don’t think there is
enough separation between the bottom of the browser window and the end of
your “page” – placing a blank, empty html item below the visible end of
your page-like construction should convince the window to give you more
“room” to display it. If not, then let me know and we’ll try adjusting this
approach.
Sorry for all the quotes - it’s my non-subtle subtle way of informing you
that in Webdesignistan, all of the print jargon that Freeway encourages you
to hang on to is the most useless crap imaginable. The sooner you let go of
it, the easier your time will be spent here.
By the way, check out my poorly-maintained portfolio (such as it is) to see
the just recent highlights of my 20+ year career –
I try to get the green-card for Webdesignistan for years - one reason that this failed yet might be, that my portfolio is simply a mess, the other one that I lost the knowledge on how layered item-construction worked.
The first thing I’d do is to check the page-length in inspector which is probably a tick too short for those pages in question. And if there is no space below the last item to fit the canvas, it’s hard to add another one below.
Ever mentioned that I’m from printing-background, too? Even from the technical background (platemaker) and not from the graphical (what I ever wanted to study)?