"Is it getting warm in here? [fans self] Do that escape chars, regex code thing again."

Gus:

I tried posting the following code:

"Why are you like this? What did you do?"<BR>"I murdered someone, Jack. My husband."<BR>"Kate."<BR>"I killed him."<BR"No."<BR>"He's dead. But this example for Gus is over."

It cut off everything after "I killed him," and when I looked at the edited post, the rest of the post was gone. The Bs in the BRs had been changed to bs, and the board was trying to close bold tags all over the place. I found the problem was a missing right caret, but it was odd that the board began to interpret the breaks as open bold tags.

Looking at your quoted text, P-C, I see an open tag at: "I killed him."

Looking at your quoted text, P-C, I see an open tag at: "I killed him."

I know. Like I said, I understand what the problem was. What I don't understand is how the board went about fixing it. What I'm saying is, I broke something. Fix it.

Lemme try something.

Here is a line
And a line

It converted the open BR to a closing bold tag, which made it think the previous BR was an open bold tag and thus converted the BR to a bR. Freaky.

Looking at your quoted text, P-C, I see an open tag at: "I killed him." < BR"

The tag-matcher will assume that " <br" is enough, although it shouldn't. Your find goes on the list for fixing, on a non-drunk-and-watching-viddies day.

Too bad there's no way to set a variable in a user's profile whether to see whitefont as white or non-white.

Thread specific, doubly so.

---

Hey, my inquiry as to the rolling of post overflow into a new post turned out to be feasable, I thought I would muse anew...

Too bad there's no way to set a variable in a user's profile whether to see whitefont as white or non-white.

It's definitely possible. We talked at one time of having user-specific stylesheets and the whitefont is, or could easily be made, a style.

Is it a style? I can't remember. Let's check:

Am I a style?

t edit Nope. It's just a font color="ffffff" substitution, but that's not a barrier.

Yeah, Jon, that's a good play. I have that part of the code open now. I could replace the font part of the 's' quickedit with a div enclosure, if we think that is way to go.

The administration of user style sheets is a larger issue, of course, but the quickedit change would lay some foundation for that day.

It should be a style anyway, just so it's not tied in the HTML to the colour of the background.

Should be a style anyway, just so it's not tied in the HTML to the colour of the background.

I'm thinking in these terms:

. spoiler { font-family: "MS Sans Serif"; color: transparent; }

Which will allow changes in background color, without losing the blinvisbility of the spoiler.