feat(kanban): convert inline-create title input to multiline textarea - #20970
feat(kanban): convert inline-create title input to multiline textarea#20970JezzaHehn wants to merge 1 commit into
Conversation
- Changed Input component to native textarea for task creation - Removed Enter-to-submit behavior (use Create button instead) - Added proper styling: border, padding, rounded corners, focus ring - 2-row default height with vertical resize and max-height cap - Escape still cancels the form
|
Looks like the "Lint" Action got rate limited and this "Tests" Action also borked for some reason? not sure what's up with that haha, presumably not related to this code but rather upstream pipeline infrastructure, but please do let me know if those failures are related to the PR itself! |
alt-glitch
added
type/feature
|
Merged via PR #21243 — your commit landed on main as b93c9f6 with your authorship preserved (rebase-merge). Thanks for the contribution! I added a small follow-up on top (commit fa58274) to restore Enter=submit / Shift+Enter=newline in the new textarea — the standard convention in Slack/Discord/GitHub. The single-line common case now still submits with Enter while you can multi-line with Shift+Enter. |
|
Many thanks! Excellent followup for Shift+Enter, that is consistent with the conventions of many other sites yes. Cheers 💚 |
3 participants
Problem
The title input in the kanban inline-create form is a single-line
<input>, making it awkward for longer task descriptions or multi-line ideas.Solution
Convert to
<textarea>with:Behavior Changes
Screenshot
Before: Single-line input, Enter submits immediately
After: 2-row textarea, Create button to submit
Second example showing expanded textarea for more space
Technical Note
This PR modifies
dist/index.jsdirectly because the kanban dashboard source (TypeScript/JSX) is not in this repository. The dashboard was added in commit c868425 and shipped only as a pre-built IIFE bundle.If maintainers have access to the source, I'm happy to provide a source-level PR instead.
Consideration
If users prefer the single-line behavior, a future PR could add a user preference toggle. This change errs on the side of multiline-friendly for task descriptions, which is the more common use case for kanban cards.