That fixed it, ita.

Whoops! Sorry about that. It looked fixed on Firefox, I swear!

OK, the lab [link] is open for testing. Go ahead and make yourself an account there, if you don't already have one, and pound away.

You should be able to:

• leave font tags open
• use unbalanced delimters on values, for example: color="blue'
• dump in a long url and have it turned into a contexted linky
• do tommyrot's font size + scare quotes + apostrophe's thing
• if you know how to override a style sheet with your browser's capability to do so (Opera users see: Tools -> Preferences -> Page style), you can set the font color of the class ".spoilers" to whatever pleases you. I suggest you download [link] and modify it as your user style sheet. Only newly created spoilers will have the overridden color.
• t b t blockquote and t br will now all close correctly, without extra closing tags.

For techies: Regex delimiters were colliding with url fields. I added code to escape/ unescape those chars. This clears up events like the one aurelia and ita had. The delimiters were pipes and %'s, now they are all slashes or square brackets.

Final note: I threw in the towel on forced hypenation of long words. The screen-widening was mostly coming from long url's, anyway, and that is pretty well covered.

Jon, no worries. I think it was something specific to Safari, since no one else said anything, and even the date and time headers were whitefonted for me, so it was very noticeable.

Thanks for trying to/fixing it!

I threw in the towel on forced hypenation of long words.

Actually, some browsers force even hyphenated words to be all on one line, so you'd have to put a space in the middle of the word to make it work. No biggie though -- easy enough for a stompy to edit it.

Is it so hard to highlight for a one-time viewing?

Apparently it is, as there is talk now of making a General Spoilers lite, because some General Spoiler people don't want to deal with whitefont, while others want to be unspoiled for some shows, while being spoiled for specific ones.

But Daniel, I think a large part of that issue is not wanting to have to do the whitefont to begin with, not just the issue of having to highlight.

::shrug:: It's only one letter per paragraph.

Moot now, I guess.

I just edited a post in natter to stop the runaway whitefont, and here's what I found there:

the original post had the tags incorrectly nested, viz:

<font color="white">

blah blah </font>

And the whitefont ran away with the spoon (in Safari, anyway). Moving the opening font tag inside the > fixed things (as, I'm guessing, would moving the closing tag to the next line), but my question is, have we always enforced incorrectly-nested tags that strictly? And should we? (the latter as a practical question and not an "if I were the queen of the universe everyone's HTML would have to validate" kinda thing.) Or was it a Safari being a hardass thing all along?

have we always enforced incorrectly-nested tags that strictly? And should we?

I'm not sure I understand the question. It's not us that's enforcing anything. It's the browser.

Or was it a Safari being a hardass thing all along?

That would be my guess.