Title: Problems with CSS
Last modified: February 7, 2017

---

# Problems with CSS

 *  [evilbolt](https://wordpress.org/support/users/evilbolt/)
 * (@evilbolt)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/)
 * Im having problems getting the white part of my blog to keep up with the text.
   Is there anyway to modify the CSS file so that it will automatically extend? (
   Make sure you maximize the window) [http://www.perpetualinsanity.net/blog/index.php](http://www.perpetualinsanity.net/blog/index.php)

Viewing 10 replies - 1 through 10 (of 10 total)

 *  [xerocool](https://wordpress.org/support/users/xerocool/)
 * (@xerocool)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106086)
 * Wow, I don’t like the background…It makes the text look weird.
 *  Thread Starter [evilbolt](https://wordpress.org/support/users/evilbolt/)
 * (@evilbolt)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106090)
 * either way, do you know how to fix it?
 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106094)
 * Have you tried adding
    background-color:#fff; to your css inside #content ?
 *  [eyeno](https://wordpress.org/support/users/eyeno/)
 * (@eyeno)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106095)
 * My eyes!!!
 *  [Lorelle](https://wordpress.org/support/users/lorelle/)
 * (@lorelle)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106225)
 * It looks like you have the center “column” too high. I can only guess that this
   DIV is called “content” or “center” or some similar name that designates the 
   column. Check in the wp-layout.css file to find out what the placement specifics
   are. Consider lowering them to 150px and playing around with that.
    One of the
   biggest (and hatest) violations of web page design is creating unfriendly absolute
   values for placement of containers, such as your columns. For instance, a width
   of 600px forces a container to be that width with no option. A container of 60%
   allows the container to stretch and narrow with the width of the parent container(
   the page in the browser window) and allows flexibility for viewing no matter 
   what kind of monitor size and resolution. Some browsers are still using 600×800
   while others are using huge screens with very wide views. Creating a 100px or
   150px top header height, you can then set the left column to a specific width
   and placement, and then set the next two columns (center and right sidebar) to
   precentages and let them fall where they may in alignment. This will also fix
   your problem with the overlapping center container since it would be pushed down
   below the header automatically. Check out [http://www.csszengarden.com/](http://www.csszengarden.com/)
   for some amazing layout designs and ideas and then visit [http://www.w3c.org](http://www.w3c.org)
   for more specific help in CSS. Remember, you aren’t the only one viewing your
   site. There is research out there that 25% of all Internet users are disabled
   or handicapped in some way and the more your site meets the web standards set
   up by the W3C, the better visibility and access for your visitors. If you are
   really interested in all of this, I have extensive link resources for finding
   out more on my site at [http://www.cameraontheroad.com/learn/web/](http://www.cameraontheroad.com/learn/web/)
   and I hope this helps. Riding myself of table-designs and going CSS was one of
   the greatest gifts I gave myself as a web owner. Lorelle
 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106226)
 * A fixed width site is not necessarily a ‘bad thing’ though.
    Using a fixed width
   gives predictability of performance, especially when image are being used for
   headers. There is a place for fluid designs and fixed width, but for my money,
   fixed width is much better. Accessibility is a combination of what it looks like
   and how it is coded. I could create a fluid, works-in-all-browsers design but
   it’s accessibility might be terrible. Equally, a fixed width could be excellent
   for all the relevant accessibility criteria. In the end though, for a personal
   page, it is the decision of the site creator 🙂
 *  [Lorelle](https://wordpress.org/support/users/lorelle/)
 * (@lorelle)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106228)
 * As I said, it is the <i>unfriendly</i> fixed and absolute values that are hated.
   Not all absolutes are equal…hee hee.
    There is a fine line to walk for web designers
   to work within the….guidelines… (called web standards) while still maintaining
   their creative freedom and meeting accessibility standards (Did you hear about
   the lawsuits in England and soon other parts of the world for lack of public 
   access (for disabled and handicapped) on government and corporate web sites! 
   Ouch! It’s the law in some countries that web sites open to the public MUST be
   accessible for everyone…whatever that means). Getting back on track with this
   thread, I do believe that the absolute values of the center column should be 
   changed to move it lower, thus uncovering the header. Another problem, found 
   frequently with fixed width layouts, that this site suffers from is when viewed
   in a small window, by low resolution setting, and in a browser with a sidebar
   open with Favorites, History, or whatever in it. The content is pushed out of
   the window to the right, hiding most if not all of the right sidebar. While creative
   design choices are not “right or wrong” in this case, because the page’s content
   doesn’t resize with the browser window, the page’s designer and owner needs to
   make a decision about the layout when this occurs. To view the right sidebar,
   the user must either resize their window or scroll horizontally, and few users
   expend that much time and effort on a web page. Keeping the fixed width, the 
   designer can move the more critical information out of the right side and put
   it in the left sidebar to ensure its visibility. It’s all a matter of understanding
   the choices and the implications of those design decisions. After all, a web 
   page continues to be a work in “process”, as the designers/owners twitch and 
   tweak it to make it work as the technology changes and the design tastes improves.
   I still shudder when I think of the first pages I designed over 12 years ago.
 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106232)
 * True… my first pages were evil too, but then all pages were pretty atrociously
   coded.
    What we have to remember I suppose is that for new people now, there 
   is so much to learn from scratch and the general standard could be seen to be
   higher along with expectations, so it is necessary for us to point and recommend
   but then stand back and allow the owner to grow and learn.
 *  [Root](https://wordpress.org/support/users/root/)
 * (@root)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106237)
 * Well it is true that essential nav elements disappear beyond the scroll bar first
   
   when the width is fixed and the view port is narrow. But most accessibility experts
   are agreed that is the best place for it – seeing as most folks are right eyed
   and right handed. The connection between flex width and accessibility can be 
   overstated. Level 2 accessibility I think it is called is achieveable with fixed
   width and would certainly meet the statutory standard in most countries. The 
   leading case is Australian – to my knowledge it has not yet been followed in 
   an English Court. I think I am right in saying the claimant was unsighted. All
   of which is OT and of no use to the poor guy who posted the question. Lets give
   him him a break as podz suggests 🙂
 *  Thread Starter [evilbolt](https://wordpress.org/support/users/evilbolt/)
 * (@evilbolt)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106255)
 * thank you all for help. Im gonna spend alot of time tomorrow trying to play with
   it. Its even worst now cuz ive modified my CSS to hell, but ill get it back eventually.
   🙂 Ill keep everyone updated.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Problems with CSS’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 10 replies
 * 6 participants
 * Last reply from: [evilbolt](https://wordpress.org/support/users/evilbolt/)
 * Last activity: [21 years, 5 months ago](https://wordpress.org/support/topic/problems-with-css-5/#post-106255)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
