![]() | |
#21
| |||||||
| |||||||
|
|
"Steve Pugh" <steve (AT) pugh (DOT) net> schrieb im Newsbeitrag news:6gl640ddqtjp7vlknkq8ukciokstla3pk3 (AT) 4ax (DOT) com... Is this close? http://steve.pugh.net/test/test57-short.html (see also http://steve.pugh.net/test/test57c-.html for latest version of the footer code but only using two columns and no background colours.) Works in most modern browsers, degrades to having the footer after the content in other browsers. If I could get it to work rather than degrade in Mac IE5 I'd be a happy man. I can't find the second example (get your lost page). |
|
Anyway the first one is astonishing! Definitely close and very creative. |
|
Anyway the background-image hack creates strange color differences on both my PC and my Mac (not in IE6/PC); |
|
you could maybe solve this by adding the background images also to #right and #content. |
|
IE 6 displays a 1 or 2 pixel gap below the footer, |
|
and Netscape 7 seems to need a lot of work to render the page. |
|
About Mac IE: On sites where I work with a content management (and thus not have a file per page but only one per template) I sometimes make a server side UA sniff and send a clean table layout version to Netscape 4, PC IE below 5 and Mac IE. If the background colors are not continued below the footer it does not look broken, and this is easy with a table layout. |
#22
| |||||
| |||||
|
|
"Markus Ernst" <derernst@NO#SP#AMgmx.ch> wrote: "Steve Pugh" <steve (AT) pugh (DOT) net> schrieb im Newsbeitrag news:6gl640ddqtjp7vlknkq8ukciokstla3pk3 (AT) 4ax (DOT) com... |
|
you could maybe solve this by adding the background images also to #right and #content. Or just see if GIFs are handled more consistently. |
|
and Netscape 7 seems to need a lot of work to render the page. The PNGs take a while to appear don't they? Heaven knows why, they're only 500 bytes. |
|
About Mac IE: On sites where I work with a content management (and thus not have a file per page but only one per template) I sometimes make a server side UA sniff and send a clean table layout version to Netscape 4, PC IE below 5 and Mac IE. If the background colors are not continued below the footer it does not look broken, and this is easy with a table layout. UA sniffing simply isn't reliable and Mac IE5 has better CSS support than Win IE5. |
|
That's the problem here - it supports more of CSS than Win IE does but not as much as Mozilla, so it sees some bits of the code that should be seen by advanced, i.e. non-IE, (hmm wonder what a screen reader would have made of that) browsers but not all of those bits. |
#23
| |||
| |||
|
|
"Steve Pugh" <steve (AT) pugh (DOT) net> schrieb im Newsbeitrag news:dc7940tjfi496obgcrt0n8ie3bhc4vf2u0 (AT) 4ax (DOT) com... Or just see if GIFs are handled more consistently. Possible, but I doubt that there is a cross-browser consistent color rendering at all, as a background color and a GIF or JPG with the same color definition are displayed differently on systems with 32678 colors while they fit perfectly on million-color-displays. |
|
The PNGs take a while to appear don't they? Heaven knows why, they're only 500 bytes. Even resizing the window takes some time, too, so it does not seem to have anything to do with loading. What dimensions do they have? |
|
I think to remember that I tried using very small background images (1 x 1 pixel) years ago as I thaught minimizing loading time, but that resulted in slowing down Netscape 4 extremely as it needed to repeat the image too many times. |
#24
| |||
| |||
|
|
CSS is GREAT for styling text but a total failure in respect of liquid layout. Sticking a footer text to the absolute bottom of the viewport is an example of fixed layout, not liquid layout. |
|
Liquid layout allows the footer to position itself at the end of the page, no matter how long or tall the page is. This is a Good Thing for various reasons that require a thread of their own. |
#25
| ||||
| ||||
|
|
That's exactly what I tried. And as you say, no joy in IE. Just try to scroll the window and you see that CSS has another definition of "bottom" as the browser. The footer scrolls and overlaps the content. And isn't that what you wanted? Fixed will make it stay at the bottom of the viewport, absolute will make it stay at the bottom of the screen (it'll go away when you scroll). |
|
By the way, we speak of the most frequently used browser and not about speech or pre-historian text only browsers ;-) A good page will not differentiate between any browser except for the presentation. Content should be structured well enough so it doesn't matter what browser is rendering it. |
|
CSS is GREAT for styling text but a total failure in respect of liquid layout. Many have had great success. |
|
Simplest things and top most essential things like a "simple" footer which appears on billion websites can't be done in CSS easily. Again, I'm a little unclear on what you mean by footer. One which is always viewable or one which is at the bottom and can be scrolled out of view? |
#26
| |||||
| |||||
|
|
Actually no. I don't see a status bar, or any other sort of footer. Though it's true I could put one there if I wanted to. But your question was about documents within the browser window, so what is your point? |
|
* Look at 90% of industry standard websites. What do you see? A footer at the bottom of each page What you are talking about? Show me *one* site that produces a footer at the bottom of each printed page. |
|
Yes - a footer at the bottom of each *web* page. Precisely. No problems there. But you were asking for a footer at the bottom of the *window* - weren't you? |
|
It provides information where users expect it by their browsing experience accumulated over years. A footer gives the layout its bottom frame. If you like it or not. It's standard. So which information that is so important to users is in this footer as standard, pray? |
|
If people are working in Word (or any other word-processor I have used) page footers do not sit at the bottom of the window. They do. Utter rubbish. They sit at the bottom of the *page*. font size=42> The PAGE </font>. Not the window. |
#27
| |||
| |||
|
|
CSS is GREAT for styling text but a total failure in respect of liquid layout. Sticking a footer text to the absolute bottom of the viewport is an example of fixed layout, not liquid layout. Well, great that you are so clever in definitions. So I apologize for not being precise enough. I meant *horizontally* liquid. Actually, you could have read this from my posting but now it is also clear for pedants ;-) Liquid layout allows the footer to position itself at the end of the page, no matter how long or tall the page is. This is a Good Thing for various reasons that require a thread of their own. I cannot find a single good reason for this behaviour. Do you find the page counter in a books also depending on the amount of content of the page? |
|
I would say, rather no. It would be soooo great if instead of chatting funny things about everything senseless, that someone could *finally* help with the problem. I assume that I am not the only one who run into trouble with this footer thing. On the other hand there are so many sites which can do it. So how, pleeeease? Peter |
#28
| |||
| |||
|
|
That's exactly what I tried. And as you say, no joy in IE. Just try to scroll the window and you see that CSS has another definition of "bottom" as the browser. The footer scrolls and overlaps the content. And isn't that what you wanted? Fixed will make it stay at the bottom of the viewport, absolute will make it stay at the bottom of the screen (it'll go away when you scroll). No, have you actually ever tried IE6 together with the bottom:0px thing? It behaves ridiculous. The footer overlays the content. By the way, we speak of the most frequently used browser and not about speech or pre-historian text only browsers ;-) A good page will not differentiate between any browser except for the presentation. Content should be structured well enough so it doesn't matter what browser is rendering it. I agree. But still no answer on my OP. CSS is GREAT for styling text but a total failure in respect of liquid layout. Many have had great success. Yes, either they say "NN4 or Mac IE go elsewhere" or they find themselves experimenting with numerous above mentioned hacks and tweaks and stylesheet switches. Simplest things and top most essential things like a "simple" footer which appears on billion websites can't be done in CSS easily. Again, I'm a little unclear on what you mean by footer. One which is always viewable or one which is at the bottom and can be scrolled out of view? If content is less to fill the browser THEN footer stay in the bottom of viewport ELSE footer should be at the end of the page (eventually out of the viewport) |
#29
| |||
| |||
|
|
* Look at your empty browser. What do you see? A status bar. This is a 'footer' If you're using your web site as a platform for distributing an application that reacts to user input in real time, it may make sense to have a status bar fixed in the display. If you're just serving ordinary web pages, there's no "status" to display. |
|
* Look on your newspaper or a book. What do you see? A footer with a page count, copyright information or whatever. In a book or publication or printed report with footers, the footers are at a fixed location because the page's are physically the same height. With a web document, pages are of variable height, and you normally display the footer (links, copyright info, etc.) at the bottom of the text, not at the bottom of the window. |
|
By invoking Word you are not explaining why you think that in a browser window, the footer should appear fixed at the bottom of the window instead of flowing at the bottom of the document. |
#30
| ||||||||
| ||||||||
|
|
Ok since you use both FB and IE, I'll make some demo pages. http://mikewilcox.curvedspaces.com/demo1.html http://mikewilcox.curvedspaces.com/demo2.html |
|
I'd hate to have to listen to a site in a speech browser that was written poorly. |
|
Well, there's more people with text browsers other than lynx, but there's also people who browse with author style sheets off and/or with their own styles. |
|
I fully agree, but tables work and CSS seems to fail in many aspects. Apparently you and I have a different version of "work." For me, "work" means it's rendered without problems on any browser, including old, broken, or alternative format browsers. |
|
IE has notoriously poor support for CSS. |
|
Hacks like these make things easier while we wait for MS to catch up. |
|
an @import switch for NN4? It's my understanding that NS4 was one of the first (the first?) browsers to implement CSS 1. This was riddled with inconsistencies, and many developers (myself included) simply don't style for it. NS4 will only get the plain (but still entirely useful) page without style from me (that, or one with few style suggestions). |
|
IE for Mac has just about as bad of support as it does on Windows. |
![]() |
| Thread Tools | |
| Display Modes | |
| |