1 On it.  Brickmuppet mentioned something about a broken template, but didn't specify which one.  I'll see if I can work it out.

Your bottom-bar is a new one; that shouldn't be possible the way the CSS is set up.  Some days - most days, lately - I think we should just shoot CSS in the head and go back to tables.

2 Uh, weird.  I was able to check Brickmuppet's site and leave a comment just fine.

3 Not sure what's going on, but if you don't mind too much I'm going to post another... six comments and see if it goes away.  Feel free to delete them later.

4 If it does go away, that points the finger at the display of that last comment of yours in the sidebar, though I can't see how that could be happening.  If not, it's something in the main section.

5 Two...

6 Three...

7 Four...

8 Five...

9 And six.

10 Darn.

11 Another bad thing: one of my spoilers wasn't being censored on the sidebar when I just looked at it. How bizarre.

12 I think there's an extra </div> being generated somehow, and that's bouncing the sidebar into the outer darkness so that it doesn't float to the right any more.  Haven't found it yet, though.

I have to disappear for a couple of hours, but I'll be back and get it fixed for you.

13 Oh, and I have confirmed that Brickmuppet's blog is fine in Firefox and broken in IE.  There are tags in Minx that will let you do that, but I don't think I've documented them anywhere, and I don't know why Brickmuppet would use them anyway.

I'm going to grab a copy of both your blogs to the test environment as soon as I get back and get things sorted out.

14

I wonder if this is a result of the particularly large number of spoiler tags in use right now. It happened after I added one.

I took a look at this page using FireFox. It's wrong there, too, but not the same. In IE7 the sidebar lands below all the normal stuff. In FireFox it lays on top of the bottom two entries.

Speaking of spoiler tags, there's also a problem with IE with a comment thread that has a spoiler in the last comment and where the comment entry box goes. I think I've mentioned it before, but it's still a problem.

When the spoiler gets opened, the comment entry box doesn't move, so text lays under it. If I click inside the comment entry box, it instantly blinks down to where it ought to be, but the "post" button doesn't move, so that's in the wrong place. The only way to really use it properly is to close the spoiler.

Anyway, you're on the case right now and I'll leave you to it. If you need to delete comments as an experiment, go ahead and do so.

15 Pixy, do you have a snapshot of this page that you can use for debugging? I want to make a couple of new posts, but I don't want to automagically "fix" what happened and make it difficult for you to trace.

16 My guess is that you have a post (or comment) which had an extraneous opening (but un-closed) div (I'm assuming that you're using divs for layout). It looks like your sidebar is part of your main div now, which is a normal result of an unclosed div.

17

There are two DIVs with id=main, and it looks like there are two extra close tags for DIVs as well. The spoiler tag also creates a DIV inside of a P sometimes, which will kick most browsers into quirks mode, if they're not there already.

Yes, the W3C validator pitches a fit on this page.

-j

18 This problem is definitely related to an unclosed div tag somewhere.  I haven't figured out where, but adding a div at the end of the main content (but before the #side div) fixes the problem.

19 Steven, go ahead and post whatever you want - I have my snapshot.

20 And thanks guys for the div-hunting. 

I've since fixed the duplicate main thingy, but Steven is running on a modified copy of the bugy version of the template.  I'll try fixing it.

21 The problem with the W3C validator is that it pitches a fit about everything.  I eventually gave up trying to make it all validate, but that now means that I can't use that tool to find problems like this.

22 The problem seems to be somewhere around the "Shingu 20: The summary" - Perhaps Steven was right about all the spoiler tags, as there are a bunch in that post and the comments...

23

It was my last spoiler post in that thread which made the formatting blow up.

But I'm concerned that all of you who are trying to find the problem will read the spoilers for Shingu. Not good; they give away the ending.

24 Got it! Comment 7 in "Shingu 20" is missing a closing DIV tag around the spoiler.

-j

25 Thanks J!  You're spot on.

Now I just have to fix it...

26 Fixed the page; fixing the code now.  Looks like I need to improve the error-checking in the BBCode module.

27 Doh!  I have the necessary checking in place; it just didn't happen because I assigned "spoiler" to the wrong tag class.

28

Did I forget to put in a close-spoiler tag on that one? Oops... (But not too much of an oops; just as well it happened, since it revealed a problem in Pixy's code.)

Pixy, thanks for your effort on this.

29 Yep.  The bbcode engine is supposed to track opened and closed tags and automatically balance them no matter what you do, so that was a bug that needed fixing.