you are probably missing some updates to the css only theme… 

http://websvn.simple-press.com/log.php?repname=Simple%3APress&path=%2Ftemplates%2Fcss-only%2F&isdir=1&

in particular, you want the ones for the signature changes…

#spMainContainer .spTopicPostSection {
    color: #4c5d77;
    background: #eff3f8;
    border: 1px solid #dddddd;
    margin: 2px;
    overflow: hidden;
    padding: 0;
    -moz-border-radius: 5px;
    -khtml-border-radius: 5px;
    -webkit-gradientborder-radius: 5px;
    border-radius: 5px;
    position: relative;
}

and

#spMainContainer .spTopicPostSection .spPostUserSignature {
    font-size: 90%;
    padding: 20px 0;
    margin: 0;
    border-top: 1px solid #DDE8EE;
}

I think its the first one that is causing the mis-alignment…

I have 1.0.5 of the CSS only theme installed, but I may have goofed and started my development of my custom theme from an earlier revision of the CSS only theme.

Are those the only changes to the theme since whatever came in the beta for WP 3.3?  It’s easier for me to make those small changes than start over from a current copy of 1.0.5.

that list is all the changes that fits on 2 pages… and goes back some time…

if you have some idea when you created yours, you can move forward from there…

thats a problem with being in alpha or beta… things will change… with RC rapidly approaching, we should hopefully be done with changes to themes unless a major bug pops up… and moving forward, we will have to be very, very wary of changes that affect existing themes… backwards compatibility will be king… when we update sp, ideally, any existing sp themes should keep chugging along fine… of course, you may not get at new features, but the existing stuff needs to work…

Those changes fixed it.  Thanks.

On your alpha/beta comment, if you update the theme, don’t you change the version # and have some change log?  I know the theme is updated from the fact that WP shows me there’s an update.  So, whether it’s a major or minor bug, as long as you change the version # to trigger the updater and document things in a change log, all is good going forward.  If you update SP and the update breaks a theme, people complain, and the theme updater kicks in.  It’s a nice model.

One unrelated comment on the CSS: there was an extended discussion on the Genesis forums about the order of lines in CSS, and the take away from that was to order alphabetically, except that a) top, right, bottom, left should always follow position and b) height should always follow width if those declarations are present.

I’ve gotten used to that approach, so for the theme I’ll contribute, I’m adopting it.

yes, when we update our themes and push out an update, we update the version number… so you will know we updated our theme…

we have historically used websvn (the site I linked to) for our changelogs…  but we have been discussing additional ways to make the changes known or viewable…  no final answer yet…  but you are right, the updater will alert you that something changed in the core themes…

order what alphabetically?  the styles themselves? right to left alpha?  or do you just mean the attributes within the styles?

Just the attributes within the styles.

It’s a not a huge deal, but I have been working with Genesis for a while and have adopted this approach as well, so looking at the SPF css made me think the house had been ransacked while I was out. 

I dont disagree at all… but then again, not likely to spend the time at this point, alphabetizing… I had spent some time looking for a tool that would do it for me, but alas, all the ones I found choke with the php code in all the themes but css only…