Add textarea type for advanced script settings#981
Merged
Conversation
Co-Authored-By: Christian <christian@bagerbach.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
Co-Authored-By: Christian <christian@bagerbach.com>
…error Co-Authored-By: Christian <christian@bagerbach.com>
…low properties Co-Authored-By: Christian <christian@bagerbach.com>
…overflow-wrap Co-Authored-By: Christian <christian@bagerbach.com>
chhoumann
pushed a commit
that referenced
this pull request
Nov 8, 2025
github-actions Bot
pushed a commit
that referenced
this pull request
Nov 14, 2025
# [2.8.0](2.7.0...2.8.0) (2025-11-14) ### Bug Fixes * restore Insert After matching for table separator rows ([#983](#983)) ([1393e6a](1393e6a)), closes [#970](#970) * support frontmatter tags in getFieldValues filtering ([#980](#980)) ([c9de468](c9de468)), closes [#927](#927) ### Features * Add embed replacement option for link placement ([#984](#984)) ([06a77a3](06a77a3)), closes [#893](#893) * add provider-native model discovery ([#982](#982)) ([f195c06](f195c06)) * add textarea type for advanced script settings ([#981](#981)) ([dc9a650](dc9a650)) * add update modal settings for major releases only ([#985](#985)) ([d63f8c9](d63f8c9)), closes [#447](#447) * add write to top of file switch for capture to active file ([#986](#986)) ([5361e6c](5361e6c)), closes [#248](#248) [#248](#248)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add textarea type for advanced script settings
Summary
Implements support for
textareainput type in advanced script settings, addressing feature request #772. This allows users to create multi-line text inputs for script settings, useful for configurations like YAML that span multiple lines.Changes:
textareato theOptiontype union inUserScriptSettingsModal.tsaddTextArea()method with CSS auto-grow behavior usingfield-sizing: contentresize: vertical,overflowY: auto,overflowX: hiddenfor vertical-only scalingmax-width: 100%,box-sizing: border-box,overflow-wrap: anywhereto lock width.userScriptSettingsModal .setting-item-control { min-width: 0; }to fix flex layout issuesetProperty()forfield-sizingto avoid TypeScript errors (property too new for TS DOM typings)Review & Testing Checklist for Human
field-sizing: contenteither works or degrades gracefully (should fall back to fixed 100px height with manual resize)Suggested Test Script
Notes
field-sizing: contentCSS property is very new (2024) and may not be supported in older Electron/Chromium versions. If unsupported, the textarea will remain at min-height (100px) with manual vertical resize available - this is acceptable progressive enhancement.min-width: autoprevented the textarea's container from shrinking. The CSS rule.userScriptSettingsModal .setting-item-control { min-width: 0; }fixes this, but should be tested to ensure it doesn't affect other settings.Link to Devin run: https://app.devin.ai/sessions/a356e7a36ce14819891354aadacebe42
Requested by: Christian (christian@bagerbach.com) / @chhoumann