Divs, CSS, and Positioning

I am “trying” to move some parts of our site away from tables by using divs and positioning. I have ran into a problem where I want my footer to appear below the longest/highest div. I thought that using the CSS “Clear: Both” would position the footer div below all other divs that preceded it. But apparently my thinking was flawed. I know that I can set the height to the container div but would prefer to have it dynamic.

Is there a way that do this or am I creating my positions div wrong?

Here is my code:

dept 1
switcher script
dept2
Features
footer

Subject: Divs, CSS, and Positioning

Check here: Exploring Footers – A List Apart

For future reference, this forum is for Notes-specific issues, not general development. Some people may choose to help you, just realize this is beyond the focus of this forum.

Subject: RE: Divs, CSS, and Positioning

Thanks for the link, I will check it out.

I appreciate your response but I disagree that this forum is not the place for my request. I “filed” my request under application development, which is exactly what I am doing in a Notes/Domino environment using domino specific elements, (as stated in my original question, I am going from notes tables (which this forum fouces on) to DIVs) however I did not want to put those in the sample code because they are:

1-company sensative

2-didn’t want to give too much information so that my code becomes confusing

3-unrelated to the issue at hand

I have also searched this forum and the internet prior to posting, and I have tried different methods in different sceneros. I did not just ask for code or the answer. I have followed the rules of etiquette in my postings and have givin back to my community by responding and trying to help others. That is the core fundamental purpose of this forum, users helping users.

I do realize that I should not expect a reponse from anyone, nor do I expect one, but if someone does help me I am extremely grateful and make it a point to let that user know, and I also let them know if it worked or not, so that other users can learn or get the information and not need to post a follow up or another post to get the solution.

And again, thanks for the link.

Subject: RE: Divs, CSS, and Positioning

Kelly, I don’t want to get into a flame war, but your initial post simply said you were moving a website from tables to divs. There was no mention of Notes or Domino being involved anywhere. My point was often people post questions here because it is a popular forum. I was simply cautioning you that if your question is not specifically Notes related it will likely not receive a response. Based on what you posted it was not clear you were working in a Notes or Domino environment.

I hope you find a solution to your issue and are willing to share it here.

– Charles

Subject: RE: Divs, CSS, and Positioning

I have many thoughts and comments but I only will say, thanks again for link.

Subject: RE: Divs, CSS, and Positioning

Kelly,

totally back you on that. Although Charles did give you helpful advice, his criticism was unfair. I’m about to put my own posting on here which is about Java servlets in a domino environment. According to him, I probably shouldn’t put that on here. But my understanding of this forum and the broad range of skills available within its readership says I should be able to do so, and could hope for a positive answer.

Tony

Subject: RE: Divs, CSS, and Positioning

Thanks Tony, appreciate your response and validation.

Good Luck on your Java servlets. I know nothing about Java or applets, but I am sure that there are many people here that will be able to help you. I haven’t seen your post, so I hope you figured it out rather then are afriad to post.

Subject: Divs, CSS, and Positioning

I don’t cascade divs within divs (doing this seems to me to be not much better than using tables or frames) so I cannot answer directly. But there is a goldmine of information in Jeffrey Zeldman’s book “Designing with Web Standards” (New Riders, May 2003).

If you cannot find any good help online, surf over to amazon.com and order up a copy.

-Richard, His Kanubic Travesty

–

======================================================================

Richard Hopley Winston-Salem, NC, USA

. rhopley[at]earthlink[dot]net

. Nothing really matters except Boats, Sex, and Rock’n’Roll

. rhopley[at]wfubmc[dot]edu

. OK, OK; computer programming for scientific research also matters

======================================================================

Subject: RE: Divs, CSS, and Positioning

If you don’t cascade divs within divs, you are probably missing structural information in the document. Adding divs for layout purposes only is as evil as the misuse of tables, but failing to add divs to mark off logical divisions (and subdivisions) within the document is not really semantic markup either, is it?

Eventually, of course, you will reach a point where the “classic” elements – lists, headings, paragraphs, etc. – are all you need, and adding divs to specify that headings are headings, say, is being needlessly and unnecessarily repetitive and redundant. Above that threshold, though, you can usually find “chunks” of the page that make up a logical grouping (an article in a newsletter, say, or a posting on a blog or forum), and if there are similar chunks on the page, they should be grouped together as another “chunk” that defines a type of content (say “news”, “sports” and “business”). None of those should be confused with the banner information or the navigation elements, so there needs to be a sementic barrier between chrome, menus and content.

Guess what – you are now three deep in nested divs without doing anything at all for the sake of layout. If you view the page in a text-only browser, everything degrades properly and the page still makes sense. More than that, though, a parsing engine can tell what’s what and where’s where – where the “meat” is, which part of the “meat” is news and which is sports, and where each story starts and ends. And it’s that relatively dumb parsing engine that we’re shooting for – if a hypothetical, blindingly stupid, machine can make sense of the structure while keeping the page human-readable without CSS, then we’ve achieved semantic markup.

(A side note: the “engine” we are designing for is strictly hypothetical. That’s because there is no standards-based method for defining content chunks in HTML or XHTML.

means nothing to a real-world machine unless it has been given the rules for your site/page. Now, if you are consistent with your tagging, you COULD give a set of rules to another party and allow them to parse the data from your page. Or you could add an RSS feed to your application, go back to tables and forget the whole thing…)