But not enough stop me from making a suggestion: Alphabetize the drop-down list?
OK. Done.
Buffy ,'Sleeper'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
But not enough stop me from making a suggestion: Alphabetize the drop-down list?
OK. Done.
Gus, if you rawked any harder you'd tilt the Earth off its axis.
Go, weremonkey, go!!!!!!!!!
I noticed "margaritaville" was still on the map, so I tried moving it.
I misspelled it.
Feel free to remove the one in Maine.
That is way cool, Gus.
The hellmouth should be directly under me. I'm in Cleveland. Someone put it in Lorain County, which never did anything to anyone so far as I can tell.
So I don't know if this is a known abnormal bug, but I forgot the endquote in my font tag (<font color="white), which resulted in the following characters' being turned into red asterisks. And in the edit, the "edit" text above the white box shows up in red as well. I don't know if this normally happens when you leave off that quotation mark, or just here, but I'm just reporting it.
Polter, misquoting never works out well.
Pretty much anytime the quotes in a tag don't match something weird will happen. At least font tags are easier to fix than a misquoted "HREF" attribute.
Also, P-C, do you know about the spoiler font quick-edit? Start a line with a lower-case s and the rest of the line is automagically white.
I know about the quick edit, but it's confusing to use because of the way returns don't induce line breaks. Everything ends up on the wrong line or running together. I'm already familiar with HTML, so I don't use the quick edit, save for quoting.
I guess I could try not to tell you that Darth Vader is Luke's father, huh?
Hey, magic. Hm. Maybe I can do this after all.
When it comes to quick-edits, I see returns not inducing line-breaks as a feature. The return ends the quick-edit but doesn't induce a line break. Otherwise, I don't see how they're connected. Even if you're not using quick-edits, you run into the same return/line-break issue.
Still say there should be some easy way to tell the board to temporarily not do the ignore-single-line-breaks thing. I'm a big fan of double line breaks most of the time, anyway, and it is very useful for quickedit, but it is very annoying when you're posting poetry or song lyrics to have to use <br> and the end of every line.
Wish we could implement our own HTML tags. Like, t poetry and t /poetry to simply turn off the single-line-break thing inside the tags, though my initial (long ago) suggestion of a quick-edit code (l, maybe (that's an ell)) to make the following line have a single line break at the end would help as well. Saves 2 whole characters per line, and 'l ' is much easer to type than "<br>", too.
Example:
l 'Twas brillig and the slithy toves
l Did gire and gimble in the wabe
l And mimsy were the borogroves...