Splitter: size of panes should be updated taking into account their limitations on splitter resize

[pharret31]

No description provided.

[Copilot]

Pull request overview

Updates Splitter’s dimension-change handling so pane sizes/layout are recalculated in a way that respects pane constraints (min/max/fixed sizes) when the splitter is resized, and expands the QUnit coverage for these scenarios.

Changes:

• Reorders _dimensionChanged() to recalculate layout, apply it to DOM, then update stored item sizes.
• Updates an existing resizing test expectation to match the new constraint-aware behavior.
• Adds a set of new tests validating that minSize/maxSize constraints are respected after splitter width changes.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/devextreme/testing/tests/DevExpress.ui.widgets/splitter.tests.js	Updates one existing resize test and adds new cases covering constraint enforcement after dimension changes.
packages/devextreme/js/__internal/ui/splitter/splitter.ts	Changes dimension-change flow to apply the recalculated layout before persisting new pane sizes.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

packages/devextreme/js/__internal/ui/splitter/splitter.ts:692

• _initialPaneSizes is only captured during _renderItems(). If a consumer sets items[i].size at runtime (especially for a resizable: false pane), the new explicit size won't be reflected in _initialPaneSizes, so subsequent dimension changes may treat it as "no explicit size" and allow it to scale. Consider updating _initialPaneSizes[index] when handling the 'size' item option change so runtime updates behave consistently.

    switch (property) {
      case 'size':
        this._layout = this._getDefaultLayoutBasedOnSize(item);
        this._idealLayout = this._layout;

        this._applyStylesFromLayout(this.getLayout());
        this._updateItemSizes();
        break;