CB bug: cutting off text after TAB

Since I'm using a mobile client, I'm regularly struggling with CB messages which only appear shortened in "normal" CB clients but normal in CB60.

I looked into the HTML source ... could it be that "\t" is translated to an (unbalanced) "<\td>" in the cb sidebar and the rest is chopped?

For reproduction, posting "test\ttest" produces:

Possible workaround: pre-filtering input with s/\t/ /g
Reasoning: The way browsers handle TAB is too random and the CB isn't meant for horizontal formatting anyway
Alternative s/\t/    /g (updatet)

Cheers Rolf

š) discussion posts don't seem to preserve tab in inline <c>code</c>, the HTML here will show test    test

Comment on CB bug: cutting off text after TAB Select or Download Code

Replies are listed 'Best First'.
Re: CB bug: cutting off text after TAB by wrog (Friar) on Jan 29, 2015 at 22:36 UTC
I'm surprised that you can even input a TAB at all, given that most browsers I use will take that as meaning "move to the next input field in the TAB-ordering"	[reply]
Re^2: CB bug: cutting off text after TAB by LanX (Saint) on Jan 29, 2015 at 22:43 UTC
Mobiles! In most occasions C&P from other websites (on Android you avoid typing) But check it out, if you switch to the second non alphanumeric symbol set, the BAR button will change to TAB. And no, pressing doesn't move to next field. Cheers Rolf PS: Je suis Charlie!	[reply]
Re^3: CB bug: cutting off text after TAB by wrog (Friar) on Jan 31, 2015 at 23:25 UTC
Possible workaround: pre-filtering input with `s/\t/ /g` seems like the right thing. I can't imagine anyone expecting TAB to actually do anything else in this context (especially since whatever it might be won't work in regular browsers anyway).	[reply] [d/l]