You have this odd construct in your CSS: #containPage { /*page I am in you*/ width:223%; margin:0 auto; } The margin setting is fine and sensible but the width is rather, um, strange. The #containPage element is, essentially, the entire page so it is naturally as wide as the browser window, then the 223% is applied and the page itself becomes more than twice as wide as the browser window. Then, all the block elements that are immediate children of #containPage will be over twice as wide as the window unless you specify or imply a width in some other way.In particular, the #NavRRT element will be too wide and the menu inside #NavRRT will float to the right all the way out of the window and you'll have to scroll horizontally to see it.
Similar positioning strangeness happens with #footer. Start by getting rid of the width:223% on #containPage. The page looks fine in Safari and Chrome if I turn off just that single piece of CSS.
UPDATE: You might want to add another inside #containPage, then add max-width, min-width, and margin: 0 auto to that to keep the main content centered and reasonably sized. Everything that is currently inside #containPage would go inside this new . If you go with this approach then you probably won't need any CSS at all on #containPage, it would just need to be around to help center the "real" page.
I thought I got rid of that. Hmm. What do you recommend putting as a width in its place?
– C. N Mar 10 at 3:46 @C.N. : You don't need a width on #containerPage at all. I added an update about putting another inside your top level container to constrain the content width.
– mu is too short Mar 10 at 3:47 Okay, so now the issue seems to be that my css file won't update. So completely different, but hopefully this will work. You are very helpful.
– C. N Mar 10 at 3:58 @C.N.: The current version looks good to me in Safari, Chrome, and Firefox (and even resizes nicely, hooray! ).
Do you have an old copy of the CSS file stuck in your cache? – mu is too short Mar 10 at 4:08 @Mu hooray! I've been clearing my cache like a crazy person, so I'm glad to know that it works for someone on the outside.
I'm going to try restarting all of my browsers. – C. N Mar 10 at 4:10.
You have to remove the margin-left from your nav LIs (it's inherited from li) and remove their widths. #nav li { margin-left: 0; width: auto! Important; }.
Also, be aware that this changes a bit how it looks in Chrome...might not matter... – JCOC611 Mar 10 at 3:21 I think the nav li fix may have just worked. Hang on to your hats. – C.
N Mar 10 at 3:33 Refreshing with anticipation – Dimitry Mar 10 at 3:34 haha. It didn't work :( it didn't seem to do much of anything except make the nav lis more relevant. – C.
N Mar 10 at 3:38 Neither did removing padding-left – C. N Mar 10 at 3:40.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.