ARG

[telophase]

Working on a blog design for work. The blog posts are staying nicely to the left, as they should. The top of the sidebar is staying nicely to the right, as it should.

The two sidebar columns below the top part of it have decided that they want to hang out in the middle of the posts, instead of staying nicely in the sidebar, and everything I do either does nothing, sends them so far to the right that they're off the browser window, or puts them below the sidebar top ... directly on top of each other.

ARG

The only light at the end of the tunnel so far is that they're CONSISTENT in their wrong placement between Firefox and IE.

Comments

[green_knight]

See my post from earlier this morning about wanting an browser/editor: load the page, double-click on a block of text to edit it, and navigate through various div tags. That way I could work out why my menu won't go where it's supposed to go...

I tend to have stray </div> tags hanging out somewhere whenever things break like this. I know that forcing items into the position where I want them is not the answer, but it can be oh so tempting...

There are times when I think longingly of <table> tags...

[telophase]

I finally figured out that it was a secondary CSS sheet that I was importing into the primary sheet that was making them do weird things.

I'm using Firebug right now for Firefox to check on my coding, and it's somewhat helpful. (Less so when it shows me that everything SHOULD be working correctly and it stll isn't...)

[green_knight]

I can't install Firebug because I'm still using an older Firefox, and they have updated all their old versions to only work with the newest release (WTF?) - but liv pointed me at the Web Developer plugin, which brings up a lot of stuff onto the screen just as I need it. It doesn't solve the riddle of why a particular div that's at the bottom of the page insists on wandering towards the top right, but, well. (Also, I'm not surprised that the nesting breaks down at some point, but I expected the breaking poing to be somewhere else. What I had worked inside one set of UL tags and broke inside the second, nested UL. Ooops.)