Conversation
Adds auto-height adjustment to the TextArea component. When `autoResize` is enabled, the textarea grows with its content using scrollHeight and stops at the optional `maxHeight` cap (defaulting to 160px), at which point it becomes scrollable. `minHeight` and `maxHeight` are applied as CSS constraints regardless of `autoResize`. Also extends the props type to include native textarea HTML attributes.
Adds auto-height adjustment to the TextArea component. When `autoResize` is enabled, the textarea grows with its content using scrollHeight and stops at the optional `maxHeight` cap (defaulting to 160px), at which point it becomes scrollable. `minHeight` and `maxHeight` are applied as CSS constraints regardless of `autoResize`. Also extends the props type to include native textarea HTML attributes.
Update MCP setup command URL from GitHub Pages endpoint to the correct production URL (forceui.brainstormforce.com/mcp).
Update MCP setup command URL from GitHub Pages endpoint to the correct production URL (forceui.brainstormforce.com/mcp).
[SUR-675] [Force-UI] Add the props for text field to auto adjust height dynamically as per the text
[SUR-675] [Force-UI] Add the props for text field to auto adjust height dynamically as per the text
Apply the unmerged Lexical Shadow DOM fix (facebook/lexical#7790) via patch-package over registry lexical@0.38.2, and fix the mention plugin's Shadow-DOM-unsafe assumptions: - Port LexicalTypeaheadMenuPlugin locally to restore the menuRenderFn API removed in lexical 0.38 (keeps the custom EditorCombobox + public menuComponent/menuItemComponent props). - Give each mention option a unique key (was '' for all), fixing keyboard nav, highlighting and the duplicate-key warning. - Use event.composedPath() for outside-click detection and shadowRoot .activeElement for blur, so clicks inside the menu aren't misread across the shadow boundary. - preventDefault on item/menu mousedown so the editor keeps selection on click (otherwise the mention can't be inserted). - Portal the menu into the editor's shadow root so its styles apply. - scrollIntoView the highlighted option directly (the #typeahead-menu document lookup is null in Shadow DOM). - Match dropdown width to the editor (border-box, 100%). - Add InsideShadowDom story mounting via a real nested React root.
Apply the unmerged Lexical Shadow DOM fix (facebook/lexical#7790) via patch-package over registry lexical@0.38.2, and fix the mention plugin's Shadow-DOM-unsafe assumptions: - Port LexicalTypeaheadMenuPlugin locally to restore the menuRenderFn API removed in lexical 0.38 (keeps the custom EditorCombobox + public menuComponent/menuItemComponent props). - Give each mention option a unique key (was '' for all), fixing keyboard nav, highlighting and the duplicate-key warning. - Use event.composedPath() for outside-click detection and shadowRoot .activeElement for blur, so clicks inside the menu aren't misread across the shadow boundary. - preventDefault on item/menu mousedown so the editor keeps selection on click (otherwise the mention can't be inserted). - Portal the menu into the editor's shadow root so its styles apply. - scrollIntoView the highlighted option directly (the #typeahead-menu document lookup is null in Shadow DOM). - Match dropdown width to the editor (border-box, 100%). - Add InsideShadowDom story mounting via a real nested React root.
…typeahead anchor Typing in consumers mounting many EditorInputs (e.g. SureRank metabox) lagged badly (~300ms/keystroke, multi-second main-thread tasks). Two compounding causes, both fixed here: - Accordion: the accessibility rework kept collapsed Accordion.Content children mounted (aria-hidden), so consumers with heavy panel content (Lexical editors) mounted everything up front and re-rendered it all on every keystroke. Keep the ARIA region element in the DOM so the trigger's aria-controls/aria-labelledby still resolve, but unmount the children via AnimatePresence while collapsed, as before v1.7.11. - EditorInput typeahead: the ported menu plugin created an anchor div on every render and appended it to document.body during render at every mount, forcing style recalcs per editor mount/unmount on heavy pages (and risking leaked divs from discarded renders). Create the anchor lazily and append it only when the menu actually opens. Also memoize the mention trigger regexes per trigger and bail out of setMenuParent when the shadow-root parent is unchanged, trimming the per-keystroke render path. Measured in the SureRank metabox repro: a fast-typed sentence went from a 15.3s main-thread task (~333ms/keystroke) to 0.38s total, with collapsed sections back to mounting zero editors.
…typeahead anchor Typing in consumers mounting many EditorInputs (e.g. SureRank metabox) lagged badly (~300ms/keystroke, multi-second main-thread tasks). Two compounding causes, both fixed here: - Accordion: the accessibility rework kept collapsed Accordion.Content children mounted (aria-hidden), so consumers with heavy panel content (Lexical editors) mounted everything up front and re-rendered it all on every keystroke. Keep the ARIA region element in the DOM so the trigger's aria-controls/aria-labelledby still resolve, but unmount the children via AnimatePresence while collapsed, as before v1.7.11. - EditorInput typeahead: the ported menu plugin created an anchor div on every render and appended it to document.body during render at every mount, forcing style recalcs per editor mount/unmount on heavy pages (and risking leaked divs from discarded renders). Create the anchor lazily and append it only when the menu actually opens. Also memoize the mention trigger regexes per trigger and bail out of setMenuParent when the shadow-root parent is unchanged, trimming the per-keystroke render path. Measured in the SureRank metabox repro: a fast-typed sentence went from a 15.3s main-thread task (~333ms/keystroke) to 0.38s total, with collapsed sections back to mounting zero editors.
…ention fix(editor-input): support Lexical mention menu in Shadow DOM
…ention fix(editor-input): support Lexical mention menu in Shadow DOM
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…typeahead anchor Typing in consumers mounting many EditorInputs (e.g. SureRank metabox) lagged badly (~300ms/keystroke, multi-second main-thread tasks). Two compounding causes, both fixed here: - Accordion: the accessibility rework kept collapsed Accordion.Content children mounted (aria-hidden), so consumers with heavy panel content (Lexical editors) mounted everything up front and re-rendered it all on every keystroke. Keep the ARIA region element in the DOM so the trigger's aria-controls/aria-labelledby still resolve, but unmount the children via AnimatePresence while collapsed, as before v1.7.11. - EditorInput typeahead: the ported menu plugin created an anchor div on every render and appended it to document.body during render at every mount, forcing style recalcs per editor mount/unmount on heavy pages (and risking leaked divs from discarded renders). Create the anchor lazily and append it only when the menu actually opens. Also memoize the mention trigger regexes per trigger and bail out of setMenuParent when the shadow-root parent is unchanged, trimming the per-keystroke render path. Measured in the SureRank metabox repro: a fast-typed sentence went from a 15.3s main-thread task (~333ms/keystroke) to 0.38s total, with collapsed sections back to mounting zero editors.
…typeahead anchor Typing in consumers mounting many EditorInputs (e.g. SureRank metabox) lagged badly (~300ms/keystroke, multi-second main-thread tasks). Two compounding causes, both fixed here: - Accordion: the accessibility rework kept collapsed Accordion.Content children mounted (aria-hidden), so consumers with heavy panel content (Lexical editors) mounted everything up front and re-rendered it all on every keystroke. Keep the ARIA region element in the DOM so the trigger's aria-controls/aria-labelledby still resolve, but unmount the children via AnimatePresence while collapsed, as before v1.7.11. - EditorInput typeahead: the ported menu plugin created an anchor div on every render and appended it to document.body during render at every mount, forcing style recalcs per editor mount/unmount on heavy pages (and risking leaked divs from discarded renders). Create the anchor lazily and append it only when the menu actually opens. Also memoize the mention trigger regexes per trigger and bail out of setMenuParent when the shadow-root parent is unchanged, trimming the per-keystroke render path. Measured in the SureRank metabox repro: a fast-typed sentence went from a 15.3s main-thread task (~333ms/keystroke) to 0.38s total, with collapsed sections back to mounting zero editors.
…ention fix(editor-input): support Lexical mention menu in Shadow DOM
…ention fix(editor-input): support Lexical mention menu in Shadow DOM
…s and perf fixes" This reverts commit b106218.
…s and perf fixes" This reverts commit b106218.
…abels Add seriesLabels prop to LineChart for translatable tooltip series names
…abels Add seriesLabels prop to LineChart for translatable tooltip series names
Update changelog.txt
Update changelog.txt
ravindrakele
approved these changes
Jun 10, 2026
Adds an optional enableTimeSelection boolean prop (default false) that renders time inputs between the calendar grid and the footer: - single: one time input that sets hours/minutes on the selected date - range: start/end time inputs for from/to (end disabled until set) - multiple: flag is ignored, no time UI Times merge into the selected Date objects via date-fns setHours/ setMinutes, so onDateSelect/onApply payloads carry the chosen time and picking a new date preserves it. Same-day ranges are kept valid: the end can never land before the start, whether completed by click or edited via the time inputs. With the flag off, behavior and output are unchanged. Includes interaction tests (play functions) covering enable/disable states, time preservation, deselect with non-midnight times, endpoint swap, same-day clamping, and payload contents; plus stories and readme documentation for the new prop.
Adds an optional enableTimeSelection boolean prop (default false) that renders time inputs between the calendar grid and the footer: - single: one time input that sets hours/minutes on the selected date - range: start/end time inputs for from/to (end disabled until set) - multiple: flag is ignored, no time UI Times merge into the selected Date objects via date-fns setHours/ setMinutes, so onDateSelect/onApply payloads carry the chosen time and picking a new date preserves it. Same-day ranges are kept valid: the end can never land before the start, whether completed by click or edited via the time inputs. With the flag off, behavior and output are unchanged. Includes interaction tests (play functions) covering enable/disable states, time preservation, deselect with non-midnight times, endpoint swap, same-day clamping, and payload contents; plus stories and readme documentation for the new prop.
…tion off Covers the pre-existing behavior paths to guarantee enableTimeSelection (default false) changes nothing: single select/deselect at midnight, range complete/deselect-from/deselect-to/endpoint-swap/same-day range, multiple add/remove, dualdate cross-month range, presets initial selected value and preset click, Apply/Cancel payloads, and zero time inputs rendered in all flag-off stories.
…tion off Covers the pre-existing behavior paths to guarantee enableTimeSelection (default false) changes nothing: single select/deselect at midnight, range complete/deselect-from/deselect-to/endpoint-swap/same-day range, multiple add/remove, dualdate cross-month range, presets initial selected value and preset click, Apply/Cancel payloads, and zero time inputs rendered in all flag-off stories.
…/force-ui into date-time-picker
[SUR-747] [Improvement] - Implement Force UI Date and Time Picker for Event Schema.
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
3 participants
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.
Description
Screenshots | Video with voice-over
Link to Figma (If applicable)
How has this been tested?
Checklist: