...at which point you discovered its weakness and fixed it...right?

Sure. Make it about me.

Anyway. Something is broken (that P-C did NOT find. He didn't!).

Seriously. Was there some change in config since the testing round? I am finding escape chars in the lab that weren't there before. This is impacting the regex code.

t apologizes for the geek-speak in front of the mundanes.

ION: Dang! The tag closing stuff seems to have stopped working. Did we not test with the current version of php, with the current php config options? People are having to close their own font tags, which is something I thought P-C had thoroughly tried to break in the lab.

Is it browser dependent, perhaps. Last night, people were complaining about open tags, and although I went back far enough that it should have affected my view, it didn't (iow, for me, your fix seemed to work as recently as last night).

apologizes for the geek talk in front of the mundanes

Nah, some of us find it a turn-on.

"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.