Yes Matt I am happy to help out. The WordPress index file is borked and that is compounded by the design error in the CSS of using position absolute for the menu.
Yes Matt I am happy to help out. The WordPress index file is borked and that is compounded by the design error in the CSS of using position absolute for the menu.
Root, you're right. Everything is so obviously borked I don't know how anyone gets anything done.
For everyone else, I found the problem. The long names in the sidebar of Alex's site like silver_is_the_new black are forcing the menu to be wider than it should be, which causes a problem in Internet Explorer. In real life this would almost never happen because really_really_really_long_names usually have spaces in them. Alex says this is fixed in the latest style switcher and he'll fix it on the example pages soon.
So no change is really required, but you can optionally add overflow: hidden; after line 146 of charleen.css and regardless of any funky items in the menu it will look the same again in Internet Explorer, Firefox/mozilla, and Opera.
I am not referring to the list item bursting right. I am referring to the footer overflow which affects a huge number of entries in the style comp. I do not know if you have checked the link you have posted to Charleen (above) in Firefox but that certainly is borked as the hundreds of users who have attempted to use many of the Alex King style sheets will testify.
It is very difficult to justify using position absolute in a blog where we do not know the lengths of the menu or the content. Furthermore the rap closes before the footer. In the default this is partially disguised because the menu has no bg color, because the scheme is full width and because there is an artificially short menu in the default install. As soon as style sheet designers or users start to alter these variables the problems become more acute. The traditional formula is to float the menu but that requires the addition of a clearer div at least. Sadly many entrants in the comp appeared to be unaware of that fact. This has effected hundreds of users of your software and may well have put off a great number of others.
Floats requires a clearer div because otherwise the footer er won't clear the float :)
See Eric Meyer on Containing Floats . And you need to ask me this ?
No those are artificial. There is no menu of any length. I can scarcely believe what I am seeing on the link to Charleen above (Firefox).
This is a very common problem. I am going to be publishing a full list of all the affected layouts on my blog shortly. I find it very difficult to believe that no one has noticed the staggering difficulties that huge numbers of users encounter with the default layout. This forum is absolutely awash with those types of question, from very frustrated users. The answers have indicated the problem and solution in every case. Podz and I must have fixed hundreds of them here, by directing users to more robust templates and by email. We have been picking up the pieces from the style comp for months. I have never complained.
I think it is a very great pity that this question has escalated in this way but I and many users of my template range are now waiting for someone to describe what the fundamental problems and useability issues with my designs are.
Are you saying I faked those screenshots?
No I am not.
A version of Charleen that uses floats instead of absolute positioning, if anyone at all cares, is available here:
http://photomatt.net/dropbox/2004/08/charleen-floats.css
Took about five minutes, but it works in every browser I tested.
BTW version 1.0 of the Charleen style used floats, I switched to absolute because I find it's better in more situations.
Well the screen shots of Charleen are on my blog and in the comments to my post *Am I mad * ? Golf has already been fixed by Stuart at the bombsite. Layouts . Does it strike any one as odd that a dedicated WP fan needs to devote a whole section of his blog to fixing up other folks designs ?
"Golf has already been fixed" - What was fixed? What was the problem?
Furthermore the failure to support a floated element with a clearer div is not confined to the footer over run. It also results in colored bgs failing to come down behind the floated element. Annoyingly this effect which is in fact proper behavior does not show in FF but it sure does in IE. As to which please refer to
Position is everything . It is not immediately visible in Golf because it has no bg color to the content. Stu will explain the necessary fix.
So there is no problem, ok then.
And the borked footer in the second? Is that because Alex doesn't understand HTML?
Too bad you are better at deploying sarcasm than spotting it.
This topic has been closed to new replies.