On Mon, 5 Feb 2024 09:31:37 GMT, Robert Lichtenberger <rlich...@openjdk.org> wrote:
> , in order to "not break things" we would have to introduce an API to users > to be able to control the number of rows they want to be taken into account. I think the UI "breaking itself" is much worse than us changing the (buggy) behavior. The user gains very little if the UI locks up for several seconds (or minutes) trying to size every row. At the same time the user might simply double click on the header again (or better, just resize the offending column like they used to do since time immemorial) once a wide cell comes into view. Basically, I don't think the new API is required in this particular case; I think it's a bug and it should either size the visible rows or (visible + some margin). Of course, there is one more operation which guarantees a lock up with large models - sorting. There is no easy solution for sorting, and that's where we *might* need new APIs. And it is a totally separate issue. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1358#issuecomment-1927330194
