in reply to CB bug: cutting off text after TAB

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"

Replies are listed 'Best First'.
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!

      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).