ubbThreads has screwed html posts at least since 6.3 (which is the first version tried)

could this finally be stopped?
posting html code such as special marks like TAB works fine in ubbclassic.
but try to make a html post which is looking correct on the screen and copy&pasteable to editor is impossible with threads' [censored] ups.

thus, the suggestion:
either stop screwing up the html-code or change your code-tag to support CODE!
code can include about everything but most importantly, it must be copy-pasteable AND the white-space must not be screwed up.

code tags won't work in any UBB product, thus I bet changing the html-screw ups is simpler than fixing the code-handling.

Please watch your language.

Please provide exact examples of filtering issues. What, exactly, is going wrong?

Are you speaking of newlines being turned into <br /> tags? This is the designed behavior.

Are you speaking of HTML entities being disabled? This is the designed behavior.

>Are you speaking of newlines being turned into <br /> tags?
>This is the designed behavior.

I can imagine what he wants to say(among other things) is that when you check "use html only" with your post, even then newlines are being turned into <br />, although this shouldn't be.

>code tags won't work in any UBB product

Wouldn't code be simply pre and /pre ?

I have 6.4 and the HTML is so screwed up I gave up trying tp post with it.

Do like so many of us have......
Give up on it.

If HTML is entered in one complete line - it works fine. Essentially you have to get rid of all spaces & returns

Even then the tables are not working properly. Besides, it's an awkward thing to do.

worked on my language and now with 6.5.1.1
I can post with html codes in my posts.

and no, I don't mean only br's but things like char codes.
tabs and carriage returns in the &#-notation.

but like said, now it thankfully seems to work.
(just updated yesterday, so maybe haven't yet just found anything on that)

so, thanks to the tweakers who didn't just give up.

Ah, yes, that. I believe I tracked down that one earlier to translation of \r\n as \n\n, though I am not sure and would need to investigate again.