2 ms·
There are lots of examples. I'll give one. A text input for a chat you're having with someone. It's very very offputting and irritating to have the browser con
by volatilitish 10y ago
There are lots of examples.
I'll give one. A text input for a chat you're having with someone. It's very very offputting and irritating to have the browser constantly cluttering the UI with suggestions about what you might want to type in that chat box before you press enter.
- gmazza 10y agoMessage input field for chat/forum would typically be <textarea>. For example - have a look at reply page source right here, on HN. And <textarea> doesn't auto-complete regardless of explicit options.
- pluma 10y agoChat input is typically single-line, submit-on-enter. Messaging apps seem to be transitioning to optional multiline but the default action for enter still seems to be submit so it's perfectly reasonable to use <input> for chat input.
- tracker1 10y agoWell, inline chat, like IRC is generally a single-line input... though I suppose you could use a textarea rows="1" and strip \n on paste, etc, that wouldn't be too bad as you're likely listening for \n to post the message anyway. Either way, not using a typical name/id for the text input would probably work better in terms of not getting suggestions...
- volatilitish 10y agoThat would indeed be the norm for forums. But not for chat. Real time chat is typically more usually a single line entry. Having auto-complete on that is irritating and utterly spoils the UI.