On Thu, 7 Sep 2023 00:51:11 GMT, John Hendrikx <jhendr...@openjdk.org> wrote:
> Are you sure you'll be needing these methods for solving the table column > resizing issues? Se here is the rules the way I see it: - For snapping the **min** constraint, we should be using snapSize, since the expected result should be the same or larger so as not to violate the constraint. - For snapping the **max** constraint, we should be using snapInnerSpace, since the expected result should be the same or smaller so as not to violate the constraint. - When both **min** and **max** constraints are set, we must pick the one than makes sense, typically the **min** one, and use the method corresponding to that. In the context of layouts, we should not have a situation when we lay out an inner Region and it goes beyond the boundaries of the enclosing container by one pixel, right? That's the rationale for having snapInnerSpace(). ------------- PR Comment: https://git.openjdk.org/jfx/pull/1190#issuecomment-1710449570
