Hi Pavel,

Thank you for taking the time to report the issues. I would argue that there is a difference between a styling issue and a functional one.

Regarding Priority: It's important to understand that there are many issues (including many more important ones).
There is no guarantee that an issue is fixed just because you have it.
And don't forget that some of the people who contribute to JavaFX do so in their free time.

Second, and perhaps most importantly: JavaFX is an open-source project, and contributions are very welcome. If this issue is important to you, I would encourage you to consider contributing a fix yourself. Third, if this issue is critical for your work or your organization, you may want to consider reaching out to Oracle or Gluon regarding support.

-- Marius


Am 02.06.2026 um 17:36 schrieb PavelTurk:
Hello everyone,

I opened issue JDK-8385778 - "TableColumnHeader: sort arrow mispositioned and label jumps when column-header has left padding".

Fortunately, it was not closed, but unfortunately its priority was set to P5 (i.e., it will not be addressed in this century). The reason for such a low priority is explained by the existence of a workaround: “Workaround: don’t set the header padding.”

I do not agree with this priority or the reasoning, as there is effectively no proper workaround here — the arrow is most likely positioned via Java code. And regarding the suggestion to simply avoid using padding, that is not a real workaround. Otherwise, almost every issue could be classified as P5.

For example: if a button does not work — “workaround: don’t use the button.” If a column is not added to a table — “workaround: don’t add the column to the table.”

We open issues precisely because something does not behave as expected when we actually try to use it. And padding is one of the most fundamental attributes of a table.

Therefore, I would suggest increasing the priority of this issue, if not to P1, then at least to P4.

Best regards, Pavel

Reply via email to