- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 22 Nov 2004 15:36:15 +0000 (UTC)
- To: "Syntactic: Jim Wilkinson" <syntactic@btinternet.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Mon, 22 Nov 2004, Syntactic: Jim Wilkinson wrote: > > For the compliant browsers it's then necessary to shift down the > document's main content on every page so that it doesn't overwrite the > header. Setting a top margin on <body> (for example) will work only for > the first page. I tried to figure out what the CSS2 spec authors had in > mind. I concluded that the @page rule may have been intended here > [Section 13.2]. Setting an @page top margin creates a page-box margin on > every page but unfortunately it shifts down the "fixed" header as well. > So I then applied a negative "top" offset to it. Although that had the > desired effect, the header, now shifted outside the <body> box, was > hidden, even when I specified overflow:visible on <body>. That the overflow is hidden is a bug in the implementations, not in the spec. > No one on css-d has come up with a solution. It's my belief that the > CSS21 spec is deficient/inconsistent. Although we're talking about a > very basic and practical item of functionality here, it may well be > decided that CSS21 should not be amended since CSS3 Paged Media appears > to address the issue through margin boxes [Section 4]. Can I ask a > member of the CSS WG to comment on and acknowledge the issue? Yes, the intention is for headers and footers to be done using the page margins from CSS3. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 22 November 2004 15:36:18 UTC