Riley ,'Lessons'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
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>blah.
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.
It's not us that's enforcing anything. It's the browser.
Thanks. I hadn't noticed this before, and I switched browsers at about the same time we started on making code changes, so I wasn't sure if it was Safari or some markup-fixing widget run amok.
That's the same thing I ended up fixing in the spoilers thread, btw.
I'm wondering, as a variant on DCJ's suggestion a way back -- is two character quickedit going against principle? I'm thinking of a specific set of cases -- those following >, to be precise.
Which'd mean that >i >s >b, would give you quotes italicised, spoiler fonted and bold, respectively.
I think that's a great idea.
Doesn't go against principle for me.
What would happen if you hit >>?