💾 Archived View for bbs.geminispace.org › u › cquenelle › 444 captured on 2023-07-22 at 18:30:56. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Longer input text fields"
My thoughts are that if the client can auto size in a fluid way, then it’s not good to try to make the server be in charge of it. I didn’t remember or notice that Lagrange handles this smoothly until @satch mentioned it.
2023-05-18 · 2 months ago
It would be great to have shortcut/button to expand the input area to half the page/full page.
2023-05-21 · 2 months ago
@shtirlic This is more of a client thing, for me that's Lagrange. If there was a "big-input" button, the type-in panel could get bigger and the insert-line-break key could change from "shift enter" to "enter".
2023-05-25 · 8 weeks ago
@cquenelle One option for that would be to repurpose the Titan upload UI for a "big input" mode. It might motivate me to improve the in-app text editing capabilities. 🙂
@cquenelle @skyjake I really like this idea of having the line break key change from enter to shift+enter when the user switches to big input mode. It would be very convenient.
Longer input text fields — I'm not proposing a spec update or anything like that, yet (as that seems unlikely). This is just more of a question. Is there anything that can be to tell a browser that an input field is long and should be displayed like a textarea preferably? For a search box or for simple question/answer type inputs the current input is appropriate. But for longer fields, such a when posting on Bubble, it should be displayed more like the tweet box on Twitter. The other solution...
💬 sirwilburthefirst · 11 comments · 2023-05-17 · 2 months ago