header an footer

[Markus Olderdissen]

each web-page contains header and footer. if the web-page contains more
then one page i want to print its header and footer to each page. but
header is only printed on first page and footer on last page. how to do
this? how can i find out how many paper is needed?

[Spartanicus]

"Garmt de Vries-Uiterweerd" <ga**********@g ooglemail.comwr ote:

>>I created a test page <http://www.phys.uu.nl/~gdevries/test/fixed/>, and
it seems that the position: fixed works fine, but the problem is that
the
fixed-positioned element overlaps the normal text

Working as designed, absolutely positioned elements are not in the flow.

Yes, that's correct. The positioning of the fixed header works the way it
should. But a header overlapping normal text is not what you want in a
practical situation, so you need a way to let the normal text begin a bit
lower, so it makes space for the header. Something like this could do the
trick:

@page { margin-top: 3cm; }
h1 { position: fixed; top: -3cm; }

But the @page rule doesn't seem to work in Opera (9.01).

The @page rule works (set a border on the body element to see),
positioning the header outside of the page box causes it to be cut off,
afaics this is allowed by the spec:

"Due to negative margin values (either on the page box or on elements)
or absolute positioning content may end up outside the page box, but
this content may be "cut" by the user agent, the printer, or ultimately,
the paper cutter."

Afaics using @page for this purpose is not appropriate, a top margin or
padding on the body wrapped in a print media rule suffices.

--
Spartanicus

[Garmt de Vries-Uiterweerd]

(X-posted and f'ups set to ciwa.stylesheet s)

On Thu, 03 Aug 2006 12:28:14 +0200, Garmt de Vries-Uiterweerd
<ga**********@g ooglemail.comwr ote:

On Thu, 03 Aug 2006 12:11:41 +0200, Spartanicus
<in*****@invali d.invalidwrote:

>"Garmt de Vries-Uiterweerd" <ga**********@g ooglemail.comwr ote:

>>I created a test page <http://www.phys.uu.nl/~gdevries/test/fixed/>,
and
it seems that the position: fixed works fine, but the problem is that
the
fixed-positioned element overlaps the normal text

Working as designed, absolutely positioned elements are not in the flow.

Yes, that's correct. The positioning of the fixed header works the way
it should. But a header overlapping normal text is not what you want in
a practical situation, so you need a way to let the normal text begin a
bit lower, so it makes space for the header. Something like this could
do the trick:

@page { margin-top: 3cm; }
h1 { position: fixed; top: -3cm; }

But the @page rule doesn't seem to work in Opera (9.01). Unless, as I
said, I'm doing something wrong, but I don't think I am.

I did some more testing, the results of which can be seen at the URL
mentioned above. My conclusion is that a number of issues make the
solution I had in mind unusable.

1) With only the rule @page { margin-top: 5cm; }, everything works as
expected: the top margin is 5cm on all pages.

2) That same @page rule inside an @media print block is completely ignored.

3) Setting position: fixed for the header, along with top: -1cm, shows
that Opera considers everything outside the page area is cut away. I think
this violates the specs, which say:

"Due to negative margin values (either on the page box or on elements) or
absolute positioning content may end up outside the page box, but this
content may be "cut" — by the user agent, the printer, or ultimately, the
paper cutter."

The page area, together with the margin area, are part of the page box.
The specs don't say that content falling outside the page area may be cut.

--
Garmt de Vries-Uiterweerd

[Garmt de Vries-Uiterweerd]

On Thu, 03 Aug 2006 14:46:07 +0200, Spartanicus <in*****@invali d.invalid>
wrote:

Your post and mine crossed each other. At the risk of repeating myself:

"Garmt de Vries-Uiterweerd" <ga**********@g ooglemail.comwr ote:

>Yes, that's correct. The positioning of the fixed header works the way
it
should. But a header overlapping normal text is not what you want in a
practical situation, so you need a way to let the normal text begin a
bit
lower, so it makes space for the header. Something like this could do
the
trick:

@page { margin-top: 3cm; }
h1 { position: fixed; top: -3cm; }

But the @page rule doesn't seem to work in Opera (9.01).

The @page rule works (set a border on the body element to see),
positioning the header outside of the page box causes it to be cut off,
afaics this is allowed by the spec:

"Due to negative margin values (either on the page box or on elements)
or absolute positioning content may end up outside the page box, but
this content may be "cut" by the user agent, the printer, or ultimately,
the paper cutter."

This quote refers to the *page box*, not the *page area*. The margin
specified inside an @page rule is the distance between the border of the
page area and the page box. The document is contained in the page area.
Content that falls outside the page box may be cut, according to the
specs, but nothing is said about content falling outside the page area.

Afaics using @page for this purpose is not appropriate, a top margin or
padding on the body wrapped in a print media rule suffices.

A top margin or padding only apply to the first page, so they won't help
on the next pages (see
http://www.phys.uu.nl/~gdevries/test/fixed/test5.html).
--
Garmt de Vries-Uiterweerd

[Spartanicus]

"Garmt de Vries-Uiterweerd" <ga**********@g ooglemail.comwr ote:

>"Due to negative margin values (either on the page box or on elements)
or absolute positioning content may end up outside the page box, but
this content may be "cut" by the user agent, the printer, or ultimately,
the paper cutter."

This quote refers to the *page box*, not the *page area*. The margin
specified inside an @page rule is the distance between the border of the
page area and the page box. The document is contained in the page area.
Content that falls outside the page box may be cut, according to the
specs, but nothing is said about content falling outside the page area.

You're right. Moz exhibits the same behaviour btw.

>Afaics using @page for this purpose is not appropriate, a top margin or
padding on the body wrapped in a print media rule suffices.

A top margin or padding only apply to the first page, so they won't help
on the next pages

My mistake.

--
Spartanicus

[Garmt de Vries-Uiterweerd]

On Thu, 03 Aug 2006 15:25:57 +0200, Spartanicus <in*****@invali d.invalid>
wrote:

"Garmt de Vries-Uiterweerd" <ga**********@g ooglemail.comwr ote:

>>"Due to negative margin values (either on the page box or on elements)
or absolute positioning content may end up outside the page box, but
this content may be "cut" by the user agent, the printer, or
ultimately,
the paper cutter."

This quote refers to the *page box*, not the *page area*. The margin
specified inside an @page rule is the distance between the border of the
page area and the page box. The document is contained in the page area.
Content that falls outside the page box may be cut, according to the
specs, but nothing is said about content falling outside the page area.

You're right. Moz exhibits the same behaviour btw.

Apart from the fact that my FF 1.5 doesn't apply the @page rule at all.

>>Afaics using @page for this purpose is not appropriate, a top margin or
padding on the body wrapped in a print media rule suffices.

A top margin or padding only apply to the first page, so they won't help
on the next pages

My mistake.

No worries. This is complicated stuff :)
--
Garmt de Vries-Uiterweerd