Neat! My last post goes into the thread header now! This is like bouncing on the bed, so fun until I break the board or ita catches me and makes me stop.
edit: I think what's happening is that when my post containing
t pre
t td class=textarea
t textarea name="message" rows="8" cols="50" wrap="PHYSICAL"
t /pre
is the last post on a page, the messages that follow it are getting sucked up into the thread header. Currently going to Jess PMoon "Buffistas Building a Better Board" Oct 30, 2002 10:58:07 pm EST makes this happen. Might be just my session. I'm using IE6.
Nou, your {td} element isn't closed, which is probably why the post goes into the header.
Okay, in Opera on the Mac, this is a really screwed up page.
Wow! That
was
weird. The mere
existence
of a
t td
t /td
pair within a post, without a
t table
t /table
pair around them, causes havoc with the tables on this page.
I fixed the post, but couldn't put in what Noumenon wanted because form tags are not allowed in posts.
The easiest way to avoid this is to disallow tables. Otherwise, it adds a new wrinkle to the tag-not-closed-in-a-post problem --- The tag
is
closed, but it's still screwing up the page.
Gack. I really don't want tables disallowed, since I use them fairly often.
But that's not good.
No, it's really not. I'm surprised the bug didn't show itself earlier.
You could be incredibly elitist and allow only admins to use tables. ;)
Unclosed font size tag here (Nevermind, fixed)
No, it's really not. I'm surprised the bug didn't show itself earlier.
I'm not all that surprised, because it's probably very rare that a <td> tag would be used in a post unless the poster was doing a table in the first place. The only reason it showed up in Noumenon's post was because he quoted a snippet of code.
I'm not sure we really have to worry about this too much right now. I'd rather see us address the problem of making sure all the open tags are closed properly first.
I'm not sure we really have to worry about this too much right now. I'd rather see us address the problem of making sure all the open tags are closed properly first.
I agree that the open tag issue should be addressed first, but this resulted in
such
a hideous error --- posts in the wrong order, pieces of posts in strange places ("Posts! Posts in new places!"), that I don't think we want to let it slide for too long.