No tabs or returns in my description

augos @augos started No tabs or returns in my description

Sep 05, 13 at 12:37am

Hello, neat site but I got a problem. My info used to enable tabs and return spaces, but now they don't no matter what I do. Can someone help me?

Amezuki @amezuki commented on No tabs or returns in my description

Amezuki @amezuki

Sep 11, 13 at 4:16pm

I believe it's because you have a > character in there somewhere. I've noticed that if you use either that or the less-than character, the site assumes that you're intending your post to be HTML rather than plaintext, and it behaves as such. Get rid of those characters, or try using at the end of each line to add a line break.

Daniel Friesen @danielfriesen commented on No tabs or returns in my description

Daniel Friesen @danielfriesen

Sep 11, 13 at 4:33pm

tags! Another forum that won't properly do paragraphs!

Amezuki @amezuki commented on No tabs or returns in my description

Amezuki @amezuki

Sep 11, 13 at 4:59pm

It'll do paragraphs, too--you just have to either enclose them in tags, or don't give the forum any reason (e.g. <> characters) to think that it should be treating your post as HTML. But deprecated though they may be, tags are easier to explain and understand if someone doesn't do HTML.

S @sugihara commented on No tabs or returns in my description

S @sugihara

Sep 11, 13 at 5:03pm

<html> <head> <style type="text/css"> h1.intro {color:blue;} p.important {color:green;} </style> </head> <body> <h1>I'm using this opportunity to see if CSS+ tags work</h1> <h2>If it does, I'm curious what the header tags will do, though the site probably has a blank CSS+ page</h2> Testing 123... As I thought, default header tags. </body> </html>

Daniel Friesen @danielfriesen commented on No tabs or returns in my description

Daniel Friesen @danielfriesen

Sep 11, 13 at 5:17pm

@Amezuki Oh no, I know about wrapping in tags, that's what I tried in that last post. But <a href="javascript:document.getElementById('main_wrapper').style.backgroundColor = '#fefefe';>this forum</a> really won't properly do paragraphs otherwise. The default (when you don't include any <> characters) is to use tags.

Sephiroth @sephiroth commented on No tabs or returns in my description

Sephiroth @sephiroth

Sep 13, 13 at 2:42pm

Right now we're kind of between the "HTML is cool! Give users freedom!" and the "Nobody knows HTML! Simplify the experience!" mindsets. Amezuki is right about the > character, which I removed and it worked (but I think you added one back). There's probably a better way to determine whether or not the user wants to use HTML, but I'm not sure if we'll continue allowing HTML at all.

Amezuki @amezuki commented on No tabs or returns in my description

Amezuki @amezuki

Sep 15, 13 at 10:51am

(dupe comment)

Amezuki @amezuki commented on No tabs or returns in my description

Amezuki @amezuki

Sep 15, 13 at 10:51am

I would personally prefer to retain HTML; there's no other way to add formatting and sometimes formatting is essential. Have you considered tracking <> pairs? One wouldn't indicate HTML; the two in that sequence anywhere in the post would be a better indicator except for rare occasions where someone is doing a bunch of math. A regexp pattern like the following should definitely identify any true HTML tag: </?\w+((\s+\w+(\s*=\s*(?:"(.|\n)*?"|'(.|\n)*?'|[^'">\s]+))?)+\s*|\s*)/?>

Haruu @haruu commented on No tabs or returns in my description

Haruu @haruu

Sep 15, 13 at 4:08pm

*Reads* ... 0___0 NO WONDER. T______T

Continue

Please login to post.

Back to Site News and Suggestions