3 ms·
Checked my whatsapp and tg, both use absolutely native inputs. The selection handles & menu, the hold-spacebar movement, the hold-to-magnify feature on ios is t
by wruza 2y ago
Checked my whatsapp and tg, both use absolutely native inputs. The selection handles & menu, the hold-spacebar movement, the hold-to-magnify feature on ios is the same as everywhere else. If that’s not native, they did a great job for nothing.
Too lazy to check on android rn, but I recently worked with the apps/chats on it and entered text, it didn’t feel different.
- saagarjha 2y agoIn fact the input field is one of the few native UI surfaces in the Telegram app.
- 1oooqooq 2y agoit's not a native widget. you can type styles on whatsapp which is not possible on native input. whatsapp is the poster child of this technique btw.
- wruza 2y agoStyles are possible with native text view, otherwise we couldn’t have fonts and colors and contenteditable and selection within <p>. I think you mistake “input core” with “web input element” here. The core I’m talking about is a text cell with characters on it that has no concept of own border. Controls like NSTextField, Win32.TextBox, GtkEntry - they all have platform text input (and output) system underneath. In case of gtk it implements it itself, cause X has none. The thing that implements all the familiar behaviors of the text input that you know. So yes, compared to HTMLInputElement these are absolutely custom. But for a platform, absolutely native.