IN ORDER TO SEE THE PICTURES, YOU'LL HAVE TO SCROLL DOWN A LOT ! (If any of you know how to fix the gap, let me know, I imported the pix directly form the gallery)
The problem is the combination of your HTML with LJ's attempt to format code.
When you make HTML tables in LJ, you can't have carriage returns between your code pieces, otherwise LJ will interpret those carriage returns. You can see if it you look at the source of your code.
BAH. It didn't work. It doesn't like the pre tags. *trying it the hard way*
blah blah
That's what it should look like if it is clean. Unfortunately, LJ mucks it up:
blah
blah
It adds those breaks because they think you want them there. Unfortunately, that's bad table code and the browser doesn't know what to do with them... so they stick them BEFORE the table as a way to alert developers that they have content that is outside the table structure.
To fix it, just eliminate all the carriage returns between the codey bits:
blahblah
Getting back to the content, yay Life on Mars folks! The pics are fabulous.
The problem is the combination of your HTML with LJ's attempt to format code.
When you make HTML tables in LJ, you can't have carriage returns between your code pieces, otherwise LJ will interpret those carriage returns. You can see if it you look at the source of your code.
BAH. It didn't work. It doesn't like the pre tags. *trying it the hard way*
blah
blah
That's what it should look like if it is clean. Unfortunately, LJ mucks it up:
blah
blah
It adds those breaks because they think you want them there. Unfortunately, that's bad table code and the browser doesn't know what to do with them... so they stick them BEFORE the table as a way to alert developers that they have content that is outside the table structure.
To fix it, just eliminate all the carriage returns between the codey bits:
blahblah
Getting back to the content, yay Life on Mars folks! The pics are fabulous.
Reply
Reply
Leave a comment