Add specification for minimum size constraints on dock manager panes

[Copilot]

Users cannot set minimum width/height for content panes and split panes. The existing CSS workaround (.sc-igc-split-pane-component-h { min-width: XXpx }) fails because splitter drag operations ignore these constraints.

Proposed API

Component-level defaults:

dockManager.minPaneWidth = 150;
dockManager.minPaneHeight = 100;
dockManager.minSplitPaneWidth = 300;
dockManager.minSplitPaneHeight = 200;

Pane-level overrides:

{
  type: 'contentPane',
  contentId: 'editor',
  minWidth: 300,
  minHeight: 200
}

Specification Documents

• FEATURE_SPEC_MIN_SIZE.md - Requirements, edge cases, testing strategy
• API_DESIGN_MIN_SIZE.md - TypeScript interfaces, usage examples for Web Components, React, Angular, Blazor
• IMPLEMENTATION_GUIDE.md - Architecture, splitter drag constraint logic, layout calculation updates, test cases
• MIN_SIZE_SUMMARY.md - Executive overview, timeline (5-6 weeks)

Key Implementation Points

1. Splitter constraint enforcement - Calculate both panes' resulting sizes during drag; stop at minimum boundary
2. Nested split panes - Minimum size = sum of children + splitter dimensions
3. Property precedence - Pane-level → Component-level → CSS variables → undefined
4. Backward compatibility - All properties optional; undefined maintains current behavior

Target: v1.19.0 (no breaking changes)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Set a minimum width for the content panes / split panes in the IgrDockManager</issue_title>
<issue_description>Issue is copy of: IgniteUI/igniteui-react#56
Created by: @jainankit2474

Thank you for contacting Infragistics Developer Support.

My team and I have done an initial review of this support case, and there does not currently exist a way to set a minimum width for the content panes / split panes in the IgrDockManager. The panes are freely resizable depending on their docked location. This is modeled after Visual Studio, which allows you to freely resize the panes down or up to essentially any size the user likes.

I did find a sort of hacky way to assign a min-width globally to all split panes via some CSS, but the splitter will not follow it, and so if you resize the splitter down past that min-width and let go, no action will be taken. The hacky way to assign this is to assign the min-width to the .sc-igc-split-pane-component-h CSS, but again, the splitter will not follow here as the splitter will continue to think that you can resize to any width / height, as that is the design of the component.

If you would like to see the ability to set a minimum size on the panes of the dock manager in Ignite UI for React, I would recommend suggesting a new feature request for this here: https://github.com/IgniteUI/igniteui-react/issues. This will place you in direct communication with our product management teams who plan and prioritize upcoming features and development based on community and user feedback.

Please let me know if you have any other questions or concerns on this matter.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Set a minimum width for the content panes / split panes in the IgcDockManager #109

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[mtsvyatkova]

@copilot Implement this feature in https://github.com/IgniteUI/dock-manager

[Copilot]

@copilot Implement this feature in https://github.com/IgniteUI/dock-manager

I understand you'd like this feature implemented in https://github.com/IgniteUI/dock-manager. However, that repository is not currently available in my environment. I'm working in the igniteui-dockmanager repository which appears to be a documentation-only public repository.

Could you clarify:

1. Should I clone and work in the dock-manager repository instead?
2. Is the dock-manager repository the private source code repository containing the actual implementation?
3. Do you have a specific branch or access setup I should use?

Currently, I've created comprehensive specifications in this repository that can guide the implementation. If you'd like me to implement the actual code changes, I'll need access to the source code repository.