Conversation
* feat: add support for Shadow DOM for DropdownContainer - Updated `UuiEnhancedApp` to accept a `shadowRootHost` for Shadow DOM integration. - Introduced a new example demonstrating UUI context usage within a Shadow DOM. - Updated documentation and type definitions to reflect the new `shadowRootHost` property. - fixed `autoFocus` always being `true` even when `false` is passed through params. * refactor: remove shadowRootHost support and update DropdownContainer focus handling - Removed `shadowRootHost` from `useUuiServices` and related components. - Updated `DropdownContainer` to manage focus lock correctly without relying on `shadowRootHost`. - Deleted example demonstrating Shadow DOM usage as it is no longer supported. - Updated changelog to reflect changes in focus handling for `DropdownContainer`. * feat: add Shadow DOM support for dropdowns * restore default autoFocus * restore autoFocus fix * feat: enhance screenshot handling in integration tests - Added `waitForImagesLoaded` method to `AbsPage` to ensure images are fully loaded before taking screenshots. - Updated `expectScreenshot` methods in `IntegrationTestPage` and `PreviewPage` to utilize the new loading method with configurable timeout. - Imported `slowTestExpectTimeout` from configuration for better control over slow test scenarios. - Updated related screenshot files to reflect changes in test execution. --------- Co-authored-by: Ivan Runets <ivan_runets@epam.com> Co-authored-by: Stanislau Matsiyeuski <stanislau_matsiyeuski@epam.com>
* Removed `SelectionUtils` from `helpers` (shadow selection helpers no longer used for toolbar placement) * Updated `PositionedToolbar`: positioned the floating toolbar using Plate `toDOMRange`; removed the obsolete props & funcs; added a note about Safari in Shadow DOM and `useEventEditorSelectors` * Updated `Toolbars` and `tablePlugin`: stopped passing `editor` into `FloatingToolbar`
Preset actions dropdown used IconButton (button) inside the tab button. Render the toggler with IconButton type=span and rely on Clickable span support so the DOM stays valid and the nesting warning goes away. Co-authored-by: Ivan Runets <ivan_runets@epam.com>
Co-authored-by: Ivan Runets <ivan_runets@epam.com>
Co-authored-by: Ivan Runets <ivan_runets@epam.com>
…536) (#3089) Resolve output path under ROOT_DIR; reject traversal outside the repository.
…3088) - Resolve paths under app/src/docs/_examples via path.relative check - Reject absolute and out-of-root paths - Fix GitHub URL when path is a string (avoid spread on string)
…al (#3090) * fix(server): harden RTE demo path resolution and prevent path traversal * chore: align version of express types
…3093) - Resolve paths under app/src/docs/_examples via path.relative check - Reject absolute and out-of-root paths - Fix GitHub URL when path is a string (avoid spread on string)
* Switched headings and default paragraph to `PlateElement` with `as`, and bold/code/italic/superscript/underline to `PlateLeaf` with `as`
* Refactored `AttachmentBlock`, `IframeBlock`, and `PlaceholderBlock` to `PlateElement` with `PlateElementProps` / `useElement` instead of manual `attributes` / `element` typing
* Updated `quotePlugin` quote renderer, `linkPlugin` anchor override, `listPlugin` `LI` component, `paragraphPlugin` default paragraph override, `NotePluginBlock`, and `Separator` to use `PlateElement` (merged `className` / styles where needed; `Separator` no longer uses `forwardRef` and applies `contentEditable={ false }` on the element)
* Replaced nested span wrappers in `baseMarksPlugin` (bold/italic/underline) with `PlateLeaf`
* Replaced inline code span in `inlineCodePlugin` with `PlateLeaf` and `PlateLeafProps`
* Wrapped `ToDoItem` in `PlateElement` with `asChild` around `FlexRow` so Slate attributes compose with the layout row
* Added `types.ts` with `TPlaceholderElement` and used `satisfies` when inserting placeholder nodes
* Todo list plugin: * Moved `checked` from `data` to the element root for todo items; updated `ToDoItem` to read and toggle `checked` there * Added `DeprecatedTTodoListItemElement`, `isLegacyTodoListItemElement`, and `migrateCheckedPropertyIfNeeded` to lift legacy `data.checked` onto the node * Added `withTodoList` and `normalizeTodoListElement` and registered them on the todo list plugin * Iframe plugin: * Updated `normalizeIframeElement` to set `url` from `url` or legacy `data.src` and to persist remaining `data` without `src` * Stopped falling back to `element.src` in `IframeBlock`; rendering uses `element.url` only * Extracted iframe `normalizeNode` wiring into `withIframe` and used it from the iframe plugin
…reference * Extracted `getVirtualReferenceElement` to separate helper file (`PositionedToolbar.helpers.ts`) * Improved virtual element positioning with `useEffect` hook and `useForceUpdate` * Added `useRef` to manage virtual target reference and ensure proper updates * Updated floating-ui middleware: added `inline()` for better text selection positioning
[RTE] PlateElement/PlateLeaf rendering and todo/iframe migration alignment
* feat(RangeDatePicker): create mobile view for RangeDatePicker * fix e2e tests * fix selected days indicator * fixes according to code review * add branch to qa list * open modal on input click * fix initial focus input --------- Co-authored-by: Ivan Runets <ivan_runets@epam.com>
Add the required post-release branch sync step to prevent version drift and merge conflicts between main and develop.
Sync/main into develop v6.5.0
…hadow dom hierarchy. the idea: 1) Existing data attr. is used for backwards compatibility: [data-shadow-host-id] 2) When same shadow DOM contains more than 1 portal root - the value of this attr. contain all the IDs separated by comma. 3) When portal root is nested under the hierarchy of shadow roots - the ID of this portal is added to all relevant nodes in this hierarchy. They are properly cleaned up when the portal root is destroyed.
* Restrict access to the metrics actuator endpoint * restrict actuator endpoints to health only
MSt1ch
approved these changes
Jun 19, 2026
|
Generated by: track-bundle-size
new sizes (raw)To set the sizes as a new baseline, you can copy/paste next content to the {
"version": "6.5.0",
"timestamp": "2026-06-19",
"sizes": {
"templateApp": {
"css": 264820,
"js": 457669
},
"@epam/app": {
"css": 726287,
"js": 4943954
},
"@epam/electric": {
"css": 2275,
"js": 2883
},
"@epam/promo": {
"css": 47756,
"js": 9145
},
"@epam/uui-extra": {
"css": 0,
"js": 213
},
"@epam/loveship": {
"css": 55336,
"js": 43224
},
"@epam/uui-components": {
"css": 25145,
"js": 244200
},
"@epam/uui-core": {
"css": 0,
"js": 338056
},
"@epam/uui-db": {
"css": 0,
"js": 42718
},
"@epam/uui-docs": {
"css": 2162,
"js": 197259
},
"@epam/uui-editor": {
"css": 12944,
"js": 164475
},
"@epam/uui-timeline": {
"css": 2199,
"js": 75104
},
"@epam/uui": {
"css": 222096,
"js": 352432
}
}
}Generated by: generate-components-api Total amount of exported types/props without JSDoc comments
|
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
6 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:
Issue link:
QA notes: