8

If you hit Shift + Enter while writing a message in Chat and continue onto the new line, when you submit your message, it will be automatically converted into a code block. bug + freehand circle

Instead, it should be left as normal text.

Improve this question
3
  • 2
    +1 , just for being productive in the face of the chat vortex.
    – Aiden Bell
    Jul 14, 2010 at 22:27
  • @Aiden if you call drawing a freehand circle productive. :)
    – Maxim Zaslavsky
    Jul 14, 2010 at 22:42
  • 1
    It's obvious that the system assumes that a multi-line message is code pasted into the textarea, I don't think all browsers let you Shift + Enter.
    – Andy E
    Jul 14, 2010 at 22:53

2 Answers 2

Reset to default
3

For info, we're experimenting with some changes to this area:

  • by default, a multi-line message (or paste) is not treated as code (so no <pre>)
  • if, however, all the lines are indented it is treated as code; a bit like the editor here
  • with a button/keypress to automatically indent etc

This should give us a fairly consistent behaviour (vs SOFU/SE), while retaining the flexiblity to post both types of message

Improve this answer
2

This is completely by design, though. The typical chat message will be a single line; anything other than that should be multiple chat messages.

Improve this answer
2
  • 2
    Still, it's tripped me up about 100% of the times I've typed a multi-line chat (admittedly, that only means 3 times). Maybe disallowing shift+enter is better in this case?
    – Edan Maor
    Jul 14, 2010 at 23:23
  • +1, I started writing an answer saying that I thought this would be by design, but demoted it to a comment instead.
    – Andy E
    Jul 14, 2010 at 23:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .