Resizing behaves strangely when the total width is less than the sum of the minSizes

[davidje13]

For example, set minSize to [300, 300] and resize the container to be smaller than 600 pixels. Dragging the divider causes it to jump between two possible sizes in reverse (i.e. dragging to the right causes it to jump to the left).

When the container size is too small, it would be more logical to consider minSizes as proportional to avoid this glitchy behaviour (so in the example above, a size smaller than 600 pixels would result in a fixed 50% / 50% split).

[nathancahill]

This one is pesky and I'm not sure what the correct behavior should be. Going to think on this proportional idea.

[davidje13]

At a high level I think there are 2 things minSize may represent:

• This pane can't show much of use if smaller than this size (e.g. text field showing less than 1 line of text), so the user shouldn't try to reduce it any further; or
• This pane's rendering breaks somehow / becomes entirely unusable if smaller than this size.

In the second case, there's not much that can be done except forcing scrolling somewhere (which wouldn't be the responsibility of this library), but in the first case it seems that inconveniencing all components equally is the best way to stay as usable as possible.