331–340 of 385 posts
- "Not-Boxes": Negatively formulated text (disable... / don't...)
- "Button-Checkboxes": Checkboxes with verbs that trigger actions
- "Radio-Checkboxes": Radios that are actually checkboxes (not mutually exclusive)
- "Toggle-Checkboxes": Checkboxes that are actually toggle buttons and can't decided wheter the text should show the current state or the state that will happen when you click.
Earlier quoted context omitted.
Microsoft teams: not as bad as people say, except for this situation. I have accidentally sent so many messages trying to get to a new line.
I also sent a LOT of Slack messages prematurely for the same reason. Used to it now, though. The more an interface emphasises the single-line nature of a text input, the better. Multi-line should never submit on enter, single-line always should.
In text boxes in some applications, enter submits the entered text, and ctrl-enter forces a newline (not at my computer, but I think Slack does this). In others, it's the other way around (pretty sure GitHub does this for comments). I don't know how we got here and I don't know how to fix it, but "bring back idiomatic design" doesn't help when we don't have enough idioms. I'm not even sure if those two behaviors are…
In Slack it can get even worse. If you turn on Markdown formatting, shift+enter adds a new line, unless you’re in a multi-line code block started with three backticks, and then enter adds a new line and shift+enter sends the message. I can see why someone thought this was a good idea, but it’s just not.
In text boxes in some applications, enter submits the entered text, and ctrl-enter forces a newline (not at my computer, but I think Slack does this). In others, it's the other way around (pretty sure GitHub does this for comments). I don't know how we got here and I don't know how to fix it, but "bring back idiomatic design" doesn't help when we don't have enough idioms. I'm not even sure if those two behaviors are…
We can easily fix this by just letting everyone choose, but no one wants to make configurable UX.
Earlier quoted context omitted.
Decades ago, Return and Enter were two different keys for that reason: Return to insert a line break, Enter to submit your input. Given the reduction to a single key, the traditional GUI rule is that Enter in a multiline/multi-paragraph input doesn’t submit like it does in other contexts, but inserts a line break (or paragraph break), while Ctrl+Enter submits. Chat apps, where single-paragraph content is the typical…
Microsoft teams: not as bad as people say, except for this situation. I have accidentally sent so many messages trying to get to a new line.
Earlier quoted context omitted.
Carriage return and line feed go way back. Tty stands for teletype. A computer was the job description of a person. It’s turtles all the way down.
What lower turtles were there? My impression was that teletypes were the first proper keyboard-based interfaces.
They (about) were, AFAIK, but using them with computers wasn’t their first usage.
https://en.wikipedia.org/wiki/Teleprinter:
“A teleprinter (teletypewriter, teletype or TTY) is an electromechanical device used to send and receive typed messages through various communications channels
[…]
Initially, from 1887 at the earliest, teleprinters were used in telegraphy. Electrical telegraphy had been developed decades earlier in the late 1830s and 1840s, then using simpler Morse key equipment and telegraph operators
[…]
With the development of early computers in the 1950s, teleprinters were adapted to allow typed data to be sent to a computer”
Even for that, there was prior art. https://en.wikipedia.org/wiki/Printing_telegraph, which used a piano-style keyboard.
The Linotype also is quite old. https://en.wikipedia.org/wiki/Linotype_machine:
“The Linotype machine operator types text on a 90-character keyboard.
[…]
In July, 1886, the first commercially used Linotype was installed in the printing office of the New York Tribune.”
In text boxes in some applications, enter submits the entered text, and ctrl-enter forces a newline (not at my computer, but I think Slack does this). In others, it's the other way around (pretty sure GitHub does this for comments). I don't know how we got here and I don't know how to fix it, but "bring back idiomatic design" doesn't help when we don't have enough idioms. I'm not even sure if those two behaviors are…
I think this one is easy to explain: it's a clash between chat idioms and forum idioms. Chats since IRC have had Enter=Send because messages were supposed to be single line, while web forums have had multiline text editors from the start so Ctrl+Enter=Send made the most sense. As the two merged, confusion and conflict was inevitable. We can easily fix this by just letting everyone choose, but no one wants to make con…
This is normal/standard behavior for multiline inputs such as the textarea, while input type=text/search/email will trigger a submit.
https://html.spec.whatwg.org/multipage/form-control-infrastr...
So basically a chat input based on web technology is saying:
"I'm a single line input, but will allow multiline editing if you ask nicely"
... checks publication date ...
... right, 2023. I think the article needs an update.